A Testers Journey

An ounce of practice is better than tons of theory

Test Plan latest version

I remember writing and reading pages and pages of test plan documents and managers running behind stake holders to update the test plan.

So this blog is going to help you create a test plan which can be maintained easily and also easily consumed by your team.

Step1: Identify the product for which you would req to write a test plan.

Step2: Split the application into features. There could be multiple features and sub-features in a product. It is your choice on how you want to categorise the features in your application

Step3: Rank (1-5) each feature in terms of their priority for the application.

Step4: Write the approximate number of test cases expected in each feature

Step5: Rank (1-5) the risks number for each feature. This is done based on the impact when a feature in the application fails

Step6: Create a mind map of test environment to be tested separately.

Step 7: Other information which is not applicable to the product can be written separately or in combination with Step 6.

Here you go !! Your test plan is ready

Couple of mind maps and a table and voila we have a test plan which can be easily consumed by any of our team member

 

 

 

Advertisements

July 3, 2017 - Posted by | Uncategorized

No comments yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: