Regression Testing (Automated)

Every application comes with its share of flaws and bugs that can only be identified by proper testing. These applications operate in a very dynamic environment with rapid release cycle modes. This is where software testing comes into play ensuring that the application is reliable and able to operate consistently under peak loads. The QA team will also make sure the potential release version meets all the functional and performance requirements before certifying the particular release.

Regression Testing for Web & Mobile Applications

The objective of regression testing is to ensure that the product remains functional across previous versions and it also verifies that the changes introduced during the new release have not introduced any new bugs. It’s often very difficult for a software programmer or a software developer to how a change in one part of the software application will result in other parts.

Common Methods of Regression Testing

  • Analyzing the application changes – The team at Xminds would analyze and understand the various changes that have occurred during updates and major version release.
  • Rerun previous tests – This is to check whether the application has changed after a release and this also checks whether the bugs that were fixed earlier resurfaced. The team would perform regression testing at different levels.
  • Testing at a Unit level
  • Testing at a System level
  • Testing at a Integration level
  • Report – The team reports the issues/bugs in issue management software (cloud-hosted) such as JIRA, which enables the stakeholders/product owner to get a hawk-eye view of the testing done in detail.


QTP, JMeter, WebLOAD, TestLink, Load Runner, Win Runner and Selenium