I am automating a web application using SILK.We have already captured the neccessary window declarations.We have also created functions in a separate functions.inc file.The scripts were running fine.
Recently the GUI of our application took a change.There has been GUI changes in many pages.
What do we do?
I thought of re-capturing the affected pages.
Since we have used some of the Identifiers in the functions directly,what best could be done.
Please recommend as I work on a tight schedule.
Re: GUI change
I don't know if there is a "proper" way to do this, but I think it would be the best to record the new pages again. You can name the elements as you did before, so your functions will work as ever.
Re: GUI change
1. Usually there's no need to recapture the world - just change the tags of the objects that were affected.
Use "Compile All" in the Run menu, but don't execute the testcases.
Select Record/Window Identifer. By moving the mouse over each object within the application you can quickly identify which objects have changed and which haven't.
If you regression run time is relative short for the affected test suites, you could also just run portions of the test suite and iteratively correct the object definitions until it runs without failing.
2. While using repeated sequences of window.window.method calls in every test case is the "standard approach" that almost everyone relies on, it is an extremely poor way to create maintainable test suites. By adopting levels of abstractions within your test hierarchy you can isolate most changes to simple one-stop edits.