Service Test projects run all the tests whenever a test run is executed. You can’t easily just execute one or a few specific tests or all failing tests. This is because it’s configured like Load Runner where each test, an action, is a part of the test but not a test in isolation.
To get around this I create a second project in my local file system and set it up the same as my test project. I then develop each script one at a time on my machine. When it works I copy and paste it into the test project and continue onto the next script. This way the only test I am waiting for is the one I am working on.
If I happen to be maintaining previously working scripts then I copy the offending test into a project by itself and work on it there. There is no point in wasting ten minutes to find out if a script fix worked.
Another time saver is to use one machine for working and another for running the tests. I have two machines at my desk. That way I can fire off a run of all test scripts as I move onto the next individual test case.
|
Ryan Boucher is a Software Inquisitor and is passionate about it. You can find a whole raft of articles and anecdotes about software testing and other topics he gets excited about. |
| Tags |
