Version control of test cases

Have you ever faced such situation as the following:

Your team has developed the system and the testing well at the initial stage. Then, your development team implemented a significant update to the software’s user interface, introducing a revamped design and navigation structure. This change necessitated an update to the existing test cases to reflect the new UI elements and ensure proper functionality testing.

How do you handle the maintenance and version control of test cases to ensure accuracy, relevance, and alignment with evolving software requirements?

The automated tests are doing regression testing, so we are always a step (or more) behind the release. We usually get a month to update all scripts before any new release again. It doesn’t really matter if it is a big release or not, there are always something “broken” after any release and we “find 'em and fix 'em”.

Business Analysts, along with Super Users, do the manual testing of any “new” functionality to ensure it works properly. Then we get their notes, or test scripts, to update our automated scripts after roll out.

1 Like