Automating QTP Test Automation Home Automation Articles Downloads QTP Gotchas Links Books Contact About Site Map
Change Happens
Change happens, get over it. After all, that's the whole reason for adopting the Agile process in the first place. The challenge for Testing is that change breaks tests. The commonest cause is changes to the User Interface, but next up is Database changes. Up to a point, you can make your tests robust enough to handle it, but the real answer lies in Automating the Automation Process. What this means is having a suite of programs that automatically detect changes and either update the other tests or at least aid you as much as possible in doing it yourself. Some examples of this would be: Checking a webpage FIRST for the presence of all required elements before using them. Checking a database FIRST for the presence of all required tables and fields before using them. You could also 'fingerprint'/audit webpages and databases in order to spot changes the moment they get implemented. |
