Skip to main content

Anubhav Bansal

Anubhav Bansal
Profile picture for user anbansal

Member for

17 years 3 months

Anubhav has 18+ years’ experience with technical and managerial roles including process enhancement (scrum), test planning, people manager, manual testing, automation (UI, WS), database testing (SQL, Oracle), performance testing (SilkPerformer, LoadRunner, JMeter), and MS SQL scripting (queries, stored procedures, functions, triggers, cursors etc).

Company
Amazon
Job Function
Quality Assurance
Job Title
QA Manager - III
Industry
Computer Software - SaaS
Interests
Agile
Cloud
Configuration Management
DevOps
Leadership
Lean
Mobile
Open Source
Performance Testing
Process Improvement
Project Management
Release Management
Software Development
Test Automation
Testing/QA
Software Testing
Country
India
Profile picture for user anbansal
Anubhav Bansal

Anubhav has 18+ years’ experience with technical and managerial roles including process enhancement (scrum), test planning, people manager, manual testing, automation (UI, WS), database testing (SQL, Oracle), performance testing (SilkPerformer, LoadRunner, JMeter), and MS SQL scripting (queries, stored procedures, functions, triggers, cursors etc).

All Articles by Anubhav Bansal

All Stories by Anubhav Bansal

Cost Effective: Pre vs Post Comparison Regression Testing Cost Effective: Pre vs Post Comparison Regression Testing

The approach to test via comparison of multiple API responses between production and test code versions is very effective and produces the required results, release over release. Improvements and changes, however, are needed to address changing needs. This is true for most if not all tech solutions; the economics principle ‘Law of Diminishing Marginal Utility’ also applies to software. A tech solution that excited stakeholders when first introduced could become stale very soon. A revamp or a new solution is needed to match evolving expectations.
Person comparing two apples An Automated Approach to Regression TestingTesting every single thing isn't feasible, so regression testing should be holistic in verification while focused in scope. A good goal is to ensure no regression issue is introduced into a critical business flow. This endeavor can benefit from automation. An automated testing approach specific to reducing regression issues can go a long way toward building a good client relationship and high brand value.