So today I am having to run automated scripts manually - part of the triage process - and I thought I had come to grips with all major vague statements which make up the automated suite. That was until I encountered the instruction to "[click] lnk2".
Whatever is being created, whether it is declaring variables, reusable test scripts, or naming objects for an automation library, remember that in a year from now someone else will be picking it up and trying to work out what on earth you were on about. The key - I am not going to preach my own flavour of conventions here - just think about it. Be proactive. Have a structure. Go back and update names which were fit for purpose but are now a bit rubbish. Otherwise you will end up with a bigger pile of rubbish. Just do it.
A blog following the arduous journey along test paths and details of the interesting, bizarre and inane encountered en route.
Subscribe to:
Post Comments (Atom)
Robot Framework, Basic Setup
Plug: Robot Framework is quick to setup, easy to write tests for, and super fast to triage failures in. The last point really sets it apart...
-
So, {} represents a dictionary, e.g. {'key': value} and we can get a value out of a Robot Framework dictionary via ${dictionar...
-
For those short on time the most significant material is in black . Elaborated this becomes Hewlett Packard’s Quality Centre eleven ...
-
The art of testing lies in the ability to put the right checks in the right places to provide the right people with information at the right...
No comments:
Post a Comment