Comprehensive Black-Box Test Plan for New Mobile Phone Features in Development Stage
1) Test Objective:
To purpose of this test plan is to check whether the requirements are met as specified.
Functional test:
All the above mentioned US1- US10.
Non-Functional Test:
Load test - Responsiveness of the UI upon using multiple apps at the same instant.
2) Scope of Testing:
1. Power button and physical features of the mobile phone.
2. The apps, Phone and Dictionary.
3. UI screen responsiveness.
4. Start-up and Good-bye display configuration.
3)In-Scope testing
As per the current requirements the functionality of screen,button reponsiveness and display features are checked
4)Out-Scope testing
The security features,battery life,hardware components functionality.
5)Roles and responsibilities
Strenght of the team is assumed to be 5
Test manager: Responsible for overall strategy , ensures co-ordination within the team. and also ensures the test plan aligned to the requirements.
Bussiness analyst: Analyse the requirements from the product owner and ensure test plan is in accordance with the requirements.
Test Lead: Responsible for checking and give the go-ahead for the test cases developed for the requirements.
Test engineer: Responsible for developing and performing of test cases and documentation of the same.
UX designer: Responsible for the design of the phone and also ensures the UI experience meets the user requirements.
6) Schedule of Test and Effort Estimation
Approval for the test cases are to be taken at the start of the day and submit the documentation of the same in the evening for validation.
1.Working of power button as per requirement- day 1
2.Working of phone app - Forenoon day 2
3.Working of dictionary app - Afternoon day 2
4.Font check and user experience tests - Day 2
| Task | Responsible person | Number of hours |
| Task 1,2,3,4 with documentation | Test engineer | 10 Hrs Hrs |
| Verification and Validation | Test Lead and Test manager | 8 Hrs |
7) Assumptions
Assuming the software(OS) and hardware components are fully functional.
The security standards of the OS meet the standard guidelines.
8) Risks
Possible malfunction of power button upon irregular amount of presses and when i contact with corrosive liquids
Slow responsiveness upon multiple app running in parallel
9) Contigency plans
If the phone comes in contact with any liquid - please approach a hardware engineer.
Malfunction of power button - Wait for few seconds and try again. If it still doesnt work approach a hardware engineer.
When phone is responding slow - using the option speed up clear the temp memory.
10)Test methodology
A combination of decision table testing and equivalence partioning technique is used.
11)Test approach
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.
Action: Power button long pressed.
Expected result: phone should turn on with logo in the middle.
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
Action: Long Press powerbutton.
Expected result: Display all the apps in a 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.
Action: Phone after power ON.
Expected result: Call the phone icon to be visible first.
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.
Action: Phone after power ON.
Expected result: Dictionary as the second icon.
US- 5: As a Product owner,when I Clicked my "call the phone" icon ,all the contacts shall be visible based on chronological order.
Action: Click the call icon.
Expected result: All the contacts in 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.
Action: Click on Dictionary icon.
Expected result: Search button to be displayed in the middle of the screen.
US- 7: As a Product owner,when I long pressed my "power on" button ,my phone shall be switched off saying "Good-Bye” Message.
Action: Long Press the power button.
Expected result: Phone to be switched off showing "Good-Bye".
US-8: As a product owner ,my font in the mobile shall always be ''calibri (Body)" and shall be of size 12.
Action: Phone when ON observe the font.
Expected result: Font must always be Calibri of Size 12.
US-9:As a Customer,I need my UI to be touch responsive.
Action: Phone when ON observe the touch response.
Expected result: Touch reponse should be < 2ms.
US-10: As a customer ,my mobile phone should have no hard buttons
Action: Observe the physical design of the phone.
Expected result: No hard buttons on the whole phone body.
12) Entry Criteria
All the tests to be performed only above the 5 percent SOC.
13) Exit criteria
100% of the test case pertaining to power button , phone and dictionary app must be passed with respect to the requirements .
20% tolerance in the response rate of app under different charge states .
20% tolerance in launch and working of app under influence of 5 medium battery consuming apps when open in background.
14) Test deliverable
Documentation of test cases and results.
Before test case execution :
Documentation of test cases developed
During :
Test reports of the test cases
After test case:
Results and analysis of the reports , prioritizing the importance of UI experience and response rate of various app under different load conditions.