Peter Vogel is a system architect and principal in PH&V Information Services. PH&V provides full-stack consulting from UX design through object modeling to database design. Peter also writes courses and teaches for Learning Tree International.
If executing scheduled tests on your Test Studio computer (or just executing long-running tests on your computer) is getting in your way, you can set up an execution server and offload test runs to it.
Scheduling your tests to run on your computer when you’re not around is obviously a good idea and surprisingly easy to do. But the benefits don’t stop there: Scheduling tests lets you run your tests on multiple web browsers and speed up your testing by using headless browser testing.
When your browser or website manages to keep Test Studio’s visual recorder from getting every keystroke you need, you have a solution: Write a coded step. And you don’t even have to learn a new SDK to do it!
Not all tests are just a continuous series of steps—sometimes you need to check what’s happened in your test and do something different: a test with conditions. Here’s how to create a conditional test that tests a variety of inputs and does the right thing when bad data is entered.