Regression testing




When you are working on a project, generally test cases become thousands in number within a very few releases.

How do you manage those and how will you decide which ones to repeat in your next releases?

Assume you developed 3 modules newly. Each module is having 50 test cases which you ran in the sprints of development of feature functionality testing cycles

Here are some of the hints to decide upon the reuse ability of the test cases.

Do's:

  • Test those modules which use the same code as the newly developed modules
  • Choose the test cases of basic operations on the modules
  • Use tagging to tag same test cases for feature functionality testing as well as regression testing
  • Choose all the corner cases of testing
  • Test for special type of data
  • Test those cases which were broken in the earlier testing cycles
  • Test with different types of user logins(Customer, Admin, Super Admin)
  • Test functionalities that send emails
  • Test functionalities that are run through cronjobs


Dont's:

  • Browser testing each module
  • UI testing
  • Testing the loading of a pop up or a window. Include testing any operation on this pop up or window which imperatively tests the loading of pop up
  • Modules whose code was not meddled with(Sanity testing these modules is a must though)

With addition of 150 new test cases to your test cases base, it will be good to choose 20% of it as Regression test cases and 10% of it as Sanity test cases.

Comments

Popular posts from this blog

Bug bounty - Simple tips and tricks

Hashing, Salting, Encoding and Encrypting

Homomorphic encryption