What is Test Plan and Test Cases in Software Testing ? Characteristics, Test Scenario, Issues, Structure, Execution, Test Template, Test Preparing.
Test Plan and Test Cases
What is Test Plan ?
Test Plan explain, what needs to be tested, why the tests are performed, how the tests are conducted, when the tests are scheduled, who does the testing.
Preparing a Test Plan :
- Test plan acts as the anchor for the execution, tracking and reporting of the entire testing project and covers.
- What needs to be tested.
- How the testing is going to be performed.
- What resources are needed for testing.
- The time line by which the testing activities will be performed.
Test Plan Template
- Test plan identifier
- Introduction
- Test items
- Features to be tested
- Features not to be tested
- Approach
- Item pass/fail criteria
- Suspension criteria and resumption requirements
- Test deliverables
- Environmental needs
- Responsibilities
- Staffing and training needs
- Schedule
- Risks and contingencies
- Approvals
Test Plan Identifier
Provides a unique identifier for the document.
Introduction
State the purpose of the plan, specify the goals and objectives.
Test Items
A list of what is to be tested.
Features to be tested
What is to be tested from the USERS viewpoint.(Based on BRS QA Manager decides the Features to be tested).
Features not to be tested
- What is NOT to be tested from the Users viewpoint.
- We need to identify and justify why the feature is not to be tested. The reasons could be that the features not to be included in this build or release of the Software.(QA Manager will decide which Features not to be tested based on BRS).
Approach
This mentions the overall test Strategy/Approach for your Test Plan.
e.g. Specify the testing method (Manual or Automated, White box or black box etc.
Item Pass/Fail Criteria
Specify the criteria that will be used to determine whether each test item (software/product) has passed or failed testing.
To define the criteria for pass and fail, consider issues such as the following :
- How Significant is the problem. Does it affect any critical function?
- How likely is it that someone will encounter the problem?
- Are there any show stopper issues?
Suspension and Resumption Criteria
Suspension criteria specify the criteria to be used to suspend all or a portion of the testing activities while resumption criteria specify when testing can resume after it has been suspended.
Example : The testing will be suspended if mandatory network link is not available. Testing activity will resume with the Network link is made available.
Test Deliverables
Are nothing but all types of documents which are used in implementing the Testing it starts with sign in to sign off.
Example : Test Plan, Test Cases, Test Log, etc...
Environmental Needs
Specify the properties of test environment, hardware, software, network, etc. List any testing or related tools.
Responsibilities
List the responsibilities of each team/role/individual.
Staffing and training needs
- How many staff members are required to do the testing ?
- What are their required skills?
- What kind of training will be required?
Schedule
- Built around the roadmap but specific to testing with testing milestones.
- When will testing start.
- What will be the targets/milestones pertaining to time.
- When will testing cycle end.
Risk and Contingencies
- Any activity that is a threat to the testing schedule is a planning risk.
- What are the contingencies( A provision for an unforeseen event) in case the risk manifests itself.
- What are the mitigation plans (Alternate plans) for the risk.
Approvals
- Specify the names and roles of all persons who must approve the plan.
- Provide space for signatures and dates. (If the document is to be printed).
TEST CASES
Test Scenario
- A Scenario is any functionality that can be tested. It is also called Test Condition or Test Possibility.
- A scenario is an idea from which we can derive possible test cases on particular functionality.
Test Cases
- A case that tests the functionality of specific object.
- Test case is a description of what to be tested, what data to be given and what actions to be done to check the actual result against the expected result.
- It is document which includes step description of I/p, o/p conditions with test data along with expected results.
Characteristics of good test cases
A good case should have the following :
- TC should start with "what you are testing".
- TC should be independent.
- TC should not contain "if" statements.
- TC should be uniform.
Issues to be considered
- All the TCs should be traceable.
- There should not be too many duplicate test cases.
- Out dated test cases should be cleared off.
- All the test cases should be executable.
Structure of test Case
It Contains :
- Identifier : A unique identifier of test case.
- Test Case Author/creator i.e. name of tester.
- Version of current test case.
- Name of the test case to identify test case purpose and scope.
- Type of testing.
- Purpose : Short description of case i.e. what functionality it checks.
- Testing environment/configuration : Hardware and software configuration.
- Pre-requisite : Initial condition.
- Finalization : Action to be done after test case is performed. E.g. if test case crashes the data base, tester should restore it before other test cases will be performed.
- Input data description.
- Expected results.
Test Case Execution
Execution and execution results plays a vital role in the testing. Each and every activity should have proof.
The following activities should be taken care :
- Number of test cases executed.
- Number of defects found.
- Screen shots of successful and failure executions should be taken in word document.
- Time taken to execute.
- Time wasted due to the unavailability of the system.
Comments
Post a Comment
Please do not enter any spam link in the comment box.