Project 1 - V&V SW Analysis - I
Q:- Write a Test plan to test features of a new mobile phone (Blackbox test) that needs to be implemented based on the following requirements. (The product is still under development stage and is yet to be UA (User Acceptance ) tested .Every other thing to be included in the test plan can be hypothetical.
US-1:As a Product owner,when long pressed the power button of the phone shall switch on with a company logo at the center of the screen.
US- 2: As a Customer,when the power button is pressed my phone is switched ON and all my icons of the APPS shall be present in the grid
US- 3: As a Product owner,when the phone is powered ON ,I shall see the "call the phone" icon as the first icon at the bottom bar of my screen.
US- 4: As a Product owner,when the phone is powered ON, I shall see the "Dictionary" icon as the second icon at the bottom bar of my screen.
US- 5: As a Product owner,when I Clicked my "call the phone" icon ,all the contacts shall be visible based on chronological order.
US- 6: As a Product owner,when I Clicked my "Dictionary icon ,a search bar shall appear at the middle of the screen to let me search the meanings of the words I desire.
US- 7: As a Product owner,when I long pressed my "power on" button ,my phone shall be switched off saying "Good-Bye” Message.
US-8: As a product owner ,my font in the mobile shall always be ''calibri (Body)" and shall be of size 12.
US-9:As a Customer,I need my UI to be touch responsive.
US-10: As a customer ,my mobile phone should have no hard buttons.
Ans:-
Aim:- Write a Test plan to test the features of a new mobile phone.
Black box testing:
- Black box testing is a technique of software testing which examines the functionality of the software without peering into its internal structure or coding. The primary source of black-box testing is a specification of requirements that is stated by the customer.
- In this method, the tester selects a function and gives input value to examine its functionality, and checks whether the function is giving the expected output or not. If the function produces the correct output, then it is passed in testing, otherwise failed. The test team reports the result to the development team and then tests the next function. After completing the testing of all functions if there are severe problems, then it is given back to the development team for correction.
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.
Importance of Test Plan:-
The following are some of the key benefits of making a 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.
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 in order to give quality software to customers. The overall objective of the test is to find as many defects as possible and to make software bug 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 of 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:
- The testing team will get proper support from the development team.
- The tester will get proper knowledge transfer from the development team.
- Proper resource allocation will be given by the company to the testing department.
-
Risk: All the risks that can happen if the assumption is breaking. For Example, in the case of wrong budget estimation, the cost may overrun. Some reason that may lead to risk is:
- Test Manager has poor management skills.
- Hard to complete the project on time.
- Lack of cooperation.
-
Backup/Mitigation Plan- If any risk is involved then the company must have a backup plan, the purpose is to avoid errors. Some points to resolve/avoid risk:
- Test priority is to be set for each test activity.
- Managers should have leadership skills.
- Training course for the testers.
-
Roles and Responsibilities: All the responsibilities and role of every member in a particular testing team has to be recorded.
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.
- Scheduling: Under this, it will record the start and the end date of each and every testing-related activity. For Example, writing test case date and ending test case date.
- Defect Tracking: 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.
-
Test Environment- It is the environment which the testing team will use i.e. 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.
Example:
- Software configuration on different operating systems, such as Windows, Linux, Mac, etc.
- Hardware Configuration depends on RAM, ROM, etc.
-
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.
Entry Condition:
- Necessary resources must be ready.
- The application must be prepared.
- Test data should be ready.
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)
{
shows Dictionary icon on second position at bottom;
}
else if( owner click on call the phone icon)
{
contacts appears in alphabetical 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;
}--------------------------------------------------*********************---------------------------------------------------------