Test case, Test Plan – Manual Testing Free Training

Welcome to the Manual Testing Free Training series. In the last tutorial, we talked about the Manual Testing and Automation Testing differences.

Please refer to the following to learn about the differences:

Manual Testing Vs Automation Testing -Manual Testing Free Training

All right!! Let’s move ahead. In this tutorial, we are going to talk about the following concepts:

1. Test case.

2. Test plan.

Test case

A test case is a series of steps or a set of execution conditions or predicted results with specifying inputs to test the correct behavior/functionality, and features of the application. The aim of a test case is to divide software functionality into a small unit of function that is testable with specified input and generate a measurable result.

A test case is a feature or function that should be executed with a specified input range, given preconditions, and generates results against expected results.

How to write a good test?

1. The test case should be accurate and tests what is intended to be tested.
2. No redundant steps should be in the test case
3. The test case should be reusable. So, you can use test case to test different applications
4. The test case should be traceable to test requirements.
5. The test case should be independent. There is no dependency in your test case, and you should be able to execute the test case in any order without dependency on another test case.
6. The test case should be easy, and clear. So other testers can understand your test case by reading once.
7. Ensure that all positive and negative scenarios cover in the test case.

Test plan

A test plan is a document detailing an approach to test a system (machine or software). It is the basis for testing any software or machine. The test plan describes important information about the test project and resources that will be used during testing efforts. It identifies features to be tested, test design technique, entry & exit criteria and testing environment, dependencies of tester and risks, as well as schedule.

The goal of the Test Plan document is to:

• Describe the approach that testing will use to test the product, and the deliverables (extract from the Test Approach).
• Break down the product into distinct areas and identify characteristics of the product that are to be tested.
• Describe the procedures to be used for testing sign-off and product release.
• Specify the tools used to test the product.
• List the resource and scheduling plans.
• Provide the contact persons’ info that is responsible for various areas of the project.
• Discover risks and contingency plans that may impact the testing of the product.
• Specify bug management procedures for the project.
• Specify criteria for acceptance of development drops to testing.

Types of Test Plan 

1. Master Test Plan: A single high-level Test plan for a testing system that unifies all other types of test plans. 

2. Testing level: Test plans for each level of Testings:

• Unit Testing
• Integration Test Plan
• System Test Plan
• Acceptance Test Plan

3. Testing Type: Testing plans for a major type of testing like performance Test plan, and security Test plan.