published by Anonymous on February 1, 2016 - 17:15
Summary
Firstly, it is absolutely necessary to regression test those areas of the application that are not being changed. Just because the code isn’t changing, it doesn’t mean that a change elsewhere is not going to impact it. Of course, a proper impact analysis of a change should highlight other areas of the application that may be affected. However, as we all know, things get missed and the first time you know about it is when something goes wrong in production and impacts your ability to do business.
published by Anonymous on January 27, 2016 - 09:32
Summary
The goal of this post is to show a possible way of organizing automation based on the development plan in order to automate tests as soon as possible, without losing sight of manual testing. The functionalities to be automated will have to be already tested manually prior to beginning.
Repeated verification of the same areas, looking for tiniest inconsistencies is a pain, as everyone knows. Here are most common challenges UI regression testing brings:
Recent comments