QA Graphic

Test Description

Help QA Test better with the expected result

The best way to write up ticket testing - for QA - is two simple steps:

  • What do you want QA to test?
  • What is the expected outcome?

What Test Expected Result

Example Test Situation

As a new user, go to Google.com and click on the Sign In Button

You should see that: English (United States) should be the default language

Simple Steps To Get

By using these steps, it gives clear guidance to the QA Team on how to properly test the code change. The "Expected Results" helps clarify the specific change that was done.

Note: QA is still free to do exploratory testing around the change - time permitted. The expected results help clarify the specific changes that were made.

In the Past…

I have encountered a lot of issues that had vague testing descriptions that lead to a lot of unnecessary interactions between QA and Dev. Basically it wasn't clear exactly what was changed and how the functionality should work.

 

Comments

Add Comments

Name:
Comment:

 

About

Weekly Tips and tricks for Quality Assurance engineers and managers. All reviews are unbiased and are based on personal use. No money or services were exchanged for the reviews posted.

Schedule

Monday Media Monday
TuesdayQA
WednesdaySnagIt for QA
ThursdayPython
FridayMacintosh
SaturdayInternet Tools
SundayOpen Topic