Quality is delighting customers
Continuous re-checking of the same areas and looking for tiniest UI issues is quite cumbersome. These are the usual difficulties you face when performing UI regression testing manually:
Automating visual regression testing could help with the problems listed above, but it brings some new challenges:
So, should you automate the UI regression testing process on your web project? It depends on its scope, time limitations, UI complexity, motivation level of your QA team and many other factors. In any case, this requires careful approach, risks estimation and finding a proper test automation tool/framework which can do the trick.
And what do you think about this dilemma? Care to tell about your experience of solving manual regression testing problems?
Few more challenges:
1. With successive regression runs, test suite becomes fairly large. Due to time and budget constraints the whole regression test suite cannot be executed.
2. Minimizing the test suite while achieving maximum test coverage remains a challenge.
3. Determination of frequency of regression tests i.e., After every change in a built or a bunch of bugs fixes, is a challenge.
Thanks for you reply! I agree with the importance of these ones. Actually, #2 is particularly painful when working with UI regression testing tools since a suite of, say, 10 tests has a bunch of repetitive steps, e.g. when you have log in. A good way to optimize this is an optional verification flag for example: if you can switch the actual verification off for a certain step, it would take less time