Welcome to the Software Testing Training series. In the last tutorial, we talked about the SDLC concept & its phases.
Please refer to the following to learn about the differences:
All right!! Let’s move ahead. In this tutorial, we will explore the following concepts:
1. Test case.
2. Test plan.
It is a series of steps, or a set of execution conditions, with specified inputs to test the correct behavior/functionality, and features of the application. The goal of a test case is to divide software functionality into a small unit of function that can be tested with specified input and generate a measurable result.
A test case is a feature or function that should be run with a set number of inputs and given certain conditions and produce results that match what you expected.
How to write a good test?
- The test case should be accurate and should test what is intended to be tested.
- The test case should not have steps that are redundant.
- The test case should be able to be reused. You can use a test case to test different application features.
- The test case should be able to be correlated with the test requirements.
- The test case should be different from the other test cases. Your test case doesn’t depend on anything else, and you should be able to run it in any order without having to worry about the next one.
- The test case should be simple and understandable. To ensure that other testers have a clear understanding of your test case by simply reading it once.
- Make sure that the test case covers all positive and negative scenarios.
Important note: we like to tell you that free tutorials are helpful to get started but if you are interested in the best online LIVE Master of Manual Testing training program from the experts, please refer to the following link:
For Instructor-led training
For Self-Driven training
A test plan is a document that outlines the testing methodology for a given system. It is the basis for testing software or machines. The test plan provides detailed information regarding the test project and the resources to be utilized during testing. It defines features to be tested, test design technique, entry & exit criteria, testing environment, dependencies of tester, and risks, as well as schedule.
The goal of the Test Plan document is to:
- Explain the methodology used by testing to evaluate the product, as well as the outcomes (taken from the Test Methodology)
- Organize the product into distinct parts and pinpoint the features of the product that need to be examined.
- Describe the procedures to be followed for testing sign-off and product release.
- Describe the tools you used to test the product.
- The resource and scheduling plans should be listed.
- Provide the contact persons information that is responsible for various areas of the project.
- Find out about risks and plans that might affect the testing of the product.
- Specify bug management procedures for the project.
- Set criteria for when development drops should be accepted for 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 Testing:
- 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.
In this article, we have discussed the Test case and Test plan. To check other stuff in this series, please refer to the following link:
Happy learning, until then!