| || |
Automated testing of a wizard
Our new app implements a complicated and flexible wizard for creating the main business entities. It allows for example to go from state A to state B and further to C and D , but alsoo to start from C then move to A and further to D...My question is : what is the best possible automation framework for a case like this? My goal is to create a modular scripts, to separate the navigation script from the scripts that are testing the separate states of the wizard...But if anyone might share her/his knowledge about situation like this I will appreciate it...
All the best
Re: Automated testing of a wizard
I think any OO test language can do this. Key is to make sure development is willing to support the automation idea. Just make sure that each page has a unique identifier. A title would be nice. But you definately need a way to identify each page.
Make sure you do not use obfuscated Java, and stick with pure non embedded MFC application. Tell development that they need to avoid embedded objects for GUI, and if they plan on obfuscated Java GUI, then forget about automating the GUI. Nothing can get around this without Build integration work. Simply put, both of these will cause massive head-aches for you.
Personally, your description would lead me to believe you'd like Silk the most. But that's just my gut feel. I know it's not good to It's generalizing things, but many people seem to agree with the bottom:
Silk -> Great programming language, pain to start, and you need to know how to code.
Robot -> Great Macro recording capability. Coding is not so great.
Mercury -> Best of both, but stabilty is not so great. If you need macro right now, and want to expand later, a good choice.
If you are thinking programming oriented, Silk is C like, and I like it. For more script minded individuals, I recommend Mercury, and for non programming guys I suggest Robot.