Project 1 - V&V SW Analysis - I
What is the Test plan:
A Test Plan is a document that consists of all future testing-related activities. It is prepared at the project level and in general, it defines work products to be tested, how they will be tested, and test type distribution among the testers. Before starting testing there will be a test manager who will be preparing a test plan. In any company whenever a new project is taken up before the tester involves in the testing the test manager of the team would prepare a test Plan
Test Plan Attributes:
There some 15 attributes in Test Plan as follow
Objective: it describes the aim of the test plan, whatever the good process and procedure they are going to follow to give quality software to customers. The overall objective of the test is to find as many defects as possible and to make software bugs free the test objective must be broken into components and sub-components.
Test Strategy: it is a crucial document that is to be performed and usually designed by the Test Manager, it helps to determine Test Effort and Test cost. Test strategy helps to determine the features that are going to be tested and the features that will not be tested. The scope can be divided into two parts:
In-Scope: The modules that are to be tested rigorously
Out-Scope: The modules that are not to be tested rigorously
Testing Methodology: The methods that are going to be used for testing depend on application to application. The testing methodology is decided based on the feature and application requirements. Since the testing terms are not standard, one should define what kind of testing will be used in the testing methodology. So that everyone can understand it
Approach: The approach to testing different software is different it deals with the flow of applications for future references.
Assumptions: in this phase, certain assumptions will be made.
Example:
Test Manager: Manages the project, takes an appropriate resource, and gives project direction.
Tester: identify the testing technique, verify the test approach, and save project cost.
9. Scheduling: Under this, it will record the start and the end date of every testing-related activity.
For example, Writing the test case date and ending the test case date.
10. Defect Trading: it is an important process in software engineering as lots of issue arises when you develop a critical system for business. If there is any defect found while testing and that defect must be given to the developer team.
11. Test Environment-It is the environment in which the testing team will use Le the list of hardware and software, while testing the application, the things which are said to be tested will be written under this section. The installation of software is also checked under this.
Exit Condition:
There should not be any major bug
Most test cases should be passed.
When all test cases are executed
Test Automation: It consists of the features that are to be automated and which features are not to be automated.
If the feature has lots of bugs then it is categorized as Manual Testing.
If the feature is frequently tested then it can be automated.
Deliverables- It is the outcome from the testing team and that is to be given to the customers at the end of the project
Before the testing phase:
Test plan document.
Test case document
Test design specification
During the testing phase
Test scripts
Test data
Error logs
After the testing phase
Test Reports
Defect Report
Installation Report
Test plan to test features of a new mobile phone:
if(owner long press the power button)
{
open the company logo at centre;
}
else if(customer press the power button)
{
open the apps in grid;
}
else if(owner power on the phone)
{
shows call the phone icon on first position at bottom;
}
else if(owner power on the phone)
}
else if( owner click on call the phone icon)
{
contacts appears in chronological order;
}
else if(owner click on Dictionary icon)
{
search bar appears at centre;
}
else if(owner long press power on button)
{
displays Good-Bye and gets switched off;
}
else if(owners phone font)
{
always in calibri with size of 12;
}
else if(customer requirement touch responsive)
{
reflects on touch;
}
else ( customer requirement no hard buttons)
{
touch screen sensitive;
}