Creating A QA Test Plan -EXPLAINED
By: The Test Lead
Tags: QA, Test Plan, Software Testing, Application Testing, Qa Testing

In the software life cycle process, before any new application is deployed to any end-users, it should be tested. Without proper testing, the application can be filled with bugs and defects and then lead to a bad user experience.

This article will cover

What is a test plan?

How do you create a test plan?

What happens after the test plan is created?

Photo by Felipe Furtado on Unsplash

What is a test plan?

Anyone who is new to the QA world may be wondering, what is a test plan. This is a fundamental question, and it is important that we define it. A test plan is a document that details the processes, coverage, resources, objectives, and schedule for testing a software product. The test plan is essentially the blueprint for all of the testing efforts that will take place. It makes sure that the software meets all of the requirements asked of it. And finally, a test plan gives a clear visual to any outside user such as a client of what the application has been tested for.

Photo by Scott Graham on Unsplash

How do you create a test plan?

The first step you should take in creating a test plan is to analyze the product that is to be tested. Next, go through the requirements presented by the product owners. At a minimum, each requirement listed should have a test scenario associated with it in the test plan. From there you would also think from an end user’s perspective about what other workflows would possibly be carried out.

For each test plan that you have, you should have test cases and test scripts. Test cases outline each individual test scenario that will be covered in the test plan. The steps to carry out each test case is called the test script. It should be as detailed as possible, so that someone who has never seen the tested application prior, will still be able to follow along.

Depending on the team structure you should also clearly define the roles of the testing and what test will be automated and which test will be manually tested. You should also keep in mind the different testing types when coming up with the test plan such as unit test, system test, and integration test. Finally, depending on the application being tested, the test plan should also state the different environments that it will test in.

Photo by Samsung Memory on Unsplash

What happens after the test plan is created?

Once the test plan is created the testing process can finally start! Pass and fail criteria should also be stated for each test in the test plan. All testing results should be documented with each run. This is important to confirm test coverage and accountability. Any test that fails should be logged as a bug and defect in your management system. It should also be communicated with your team and discussed if it will be fixed before or after the application release.

Once a previous bug or defect is fixed it should go back through the testing phase. You should not only test the specific area where the bug or defect was found but also the other core functionality again. Often when something is fixed, the required change may have had an indirect effect on other parts of the application.