Project 1 - V&V SW Analysis - I
ABINAYA MAM
SOFTWARE TESTING – TEST PLAN
TEST PLAN
A test plan is a document that consists of all future testing-related activities. It is prepared at the project level.
BENEFITS OF MAKING TEST PLAN
- It acts as a quick guide for the testing process.
- It helps to avoid out-of-scope functionalities.
- It determines the time, cost, and effort.
- Provide a schedule for testing activities.
- Resource requirement and equipment.
- Test Plan Document can be used for similar projects.
- It helps to understand the test details.
- It helps in determining the quality of software applications.
TYPES OF TEST PLAN
Master Test Plan- In this type of test plan, includes multiple test strategies and has multiple levels of testing.
Phase Test Plan- In this type of test plan, emphasis on any one phase of testing.
Specific Test Plan- In this type of test plan, it is designed for specific types of testing especially non-functional testing.
TEST PLAN ATTRIBUTES
There are 15 standard test plan attributes. They are
1.OBJECTIVE:
It describes the aim of the project.
Lists all the functionality, performed to be tested.
2.TEST STRATEGY:
It is a crucial document that is to be performed.
It helps to determines the test effort, test cost and test features to be tested and not tested.
Scope is 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.
3.TESTING METHODOLOGY:
The methodology is decided based on the feature and application requirements.
It is not standard.
4.APPROACH:
It deals with flow of applications for future references.
It has two aspects:
High level scenario
The flow graph
5.ASSUMPTIONS:
Assumptions will be made.
6.RISK:
All the risks that can happen if the assumption is breaking.
7.BACK UP/MITIGATION PLAN:
If any risk is involved then the company must have a backup plan, the is to avoid errors.
8.ROLES AND RESPONSIBILITIES:
All the roles and responsibilities of every member in a particular testing team has to be recorded.
9.SCHEDULING:
It will record the start and end date of each and every testing related activity.
10.DEFECT TRACKING:
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.
Methods for the process of defect tracking:
Information capture
Prioritize
Communicate
Environment
11.TEST ENVIRONMENT:
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.
12.ENTRY AND EXIT CRITERIA:
The set of conditions that should be met in order to start any new type of testing or to end any kind of testing.
13.TEST AUTOMATION:
It consists of the features that are to be automated and which features are not be automated.
14.TEMPLATED:
It is followed by every kind of report that is going to be prepared by the testing team.
15.DELIVERABLES:
It is outcome from the testing team and that is to be given to the customers at the end of the project.
BEFORE TESTING PHASE
Test plan document
Test case document
Test design specification
DURING TESTING PHASE
Test scripts
Test data
Error logs
AFTER TESTING PHASE
Test Reports
Defect report
Installation report
TEST PLAN TO TEST THE FEATURES OF MOBILE PHONE:
1.OBJECTIVE:
AIM: To test the features of mobile phone
2.SCOPE OF TESTING:
In scope features: Ensure the power on, power off, alert messages, font style and size, priority for icon slides.
3.ROLES AND RESPONSIBLE:
Ensure all testers and test manager have red the aim of the features and list of features which are going to be performed according to the requirement.
4.SCHEDULE OF TEST:
Note down the start date and end date of test process.
Set target to complete the activities every day.
5.ASSUMPTIONS:
List the expecting outcomes (Features hierarchy, speed of operation, delay time)
6.RISKS:
Ensure Environment resource availability. If the expected plan deviates, to solve the involve the technical skilled people in the team.
7.TEST METHEODOLOGY:
Fix the type of test design technique which is going to be implemented.
8.ENTRY AND EXIT CRITERIA:
Test preconditions: Set the adequate settings, Reset the values which want to change frequent change
Software testing life cycle
9.DEFECT TRACKING:
JIRA (Journal of Indian Rheumatology Associations)
10.TEST DELIVERANCE:
Prepare documents
Errors we faced
Have a detailed report of the test plan which elaborate the entire steps taken for the development.
MOBILE PHONE FEATURES WHICH WILL EXECUTED:
If (power button is long pressed)
Then (Phone shall switch on with company logo at center of the screen)
If (power button is pressed)
Then (Phone is switched on and all my icons of the apps shall be present in the grid)
If (Phone is powered on)
Then (show call the phone icon as the first icon at the bottom bar of my screen,
Show the dictionary icon as the second icon at the bottom bar of my screen)
If (Clicked the call the phone option)
Then (all the contacts shall be visible based on the chronological order)
If (Clicked the Dictionary icon)
Then (search bar shall appear at the middle of the screen to let the user search the meaning of the word)
If (Power button is long pressed)
Then (phone shall be switched off with good-bye message)
Default (font be Calibri and size of 12,
UI to be touch responsive,
Mobile phone should have no hard buttons)