Avoid these mistakes to build automation that survives UI changes, validates outcomes properly, and provides useful feedback.

All QA professionals know the difference between a test script and a test case and the overlap between them, but few have the patience to analyze each. It can speed up testing and make tests more ...

The (narrow but very important) problem: Test scripts used for version 1.0 of an application will probably break when applied to version 2.0 of that application. Testers try to edit old test scripts ...

Protocol analyzers, data generators, voice-over-IP (VoIP) testers, and other test equipment come with graphical user interfaces (GUIs). Generally, a GUI is all you need to run many test applications, ...

Scenarios are never the same, and neither should be your Pester scripts to test those scenarios. There are a couple of ways to account for these different scenarios. You could create a separate test ...

When you write a PowerShell script how do you truly know it worked? Do you define it to be successful when it doesn't throw an error? If so, what about those times when you might have accidentally ...

Imagine typing out a series of steps in plain English that would reflect a list of actions a human QA tester would undertake to test an app, then turning that list into an automated testing script.

The instructions in a test program. It defines the actions and pass/fail criteria. For example, if the action is "to enter a valid account number," the expected result is that the data are accepted.