Project 1 - V&V SW Analysis - I
AIM: TO TEST THE FEATURES OF THE NEW MOBILE PHONE
TEST METHOD: BLACK BOX TESTING
TEST PLAN:
1. Test objective:
To test the functionality of the new mobile based on the given requirements
2. Scope of testing:
The testing will cover the features related to powering on/off, icon display, application functionality, UI responsiveness, and font settings.
3. In-scope features:
Power On/Off functionality.
Icon display on the home screen.
Bottom bar icons.
Contact display functionality.
Dictionary search functionality.
Power Off confirmation message.
Font settings.
Touch responsiveness.
Absence of hard buttons.
4. Out-of-scope features:
Detailed hardware testing
Network related functionalities
5. Roles and responsibilities of team:
Test Lead/manager: Test planning, co-ordination
Testers: Executing test cases, reporting defects
Developers: Fixing the reported defects
Stake holders: analysing the test results
6. Schedule of tests
Start Date: plan start date
End date: plan completion date. (If we are doing unit test, till when the unit test gets completed).
7. Assumptions:
System Stability:
Assumption: The mobile phone software is assumed to be in a stable state for testing, with basic functionalities operational.
Test Environment:
Assumption: The required test environment, including the mobile phone hardware and necessary software configurations, will be available and set up for testing.
8. Risks:
Resource Availability: The unavailability or scarcity of team members, including testers and developers, may impact the testing schedule.
Technical Knowledge: Insufficient knowledge or experience in handling specific technologies or components could lead to delays in identifying and fixing issues.
Test Environment Availability: Delays in setting up or unavailability of the test environment might hinder the testing process.
Data Dependency: Test data availability and quality might impact the thoroughness of testing.
9. Mitigation/Contigency plans:
Resource Availability: Cross-train team members to ensure knowledge sharing. Maintain a backup plan for key roles.
Technical Knowledge: Encourage knowledge-sharing sessions and training programs. Leverage external expertise if required.
Test Environment Availability: Proactively work with IT and other teams to set up the test environment well in advance.
Data Dependency: Create synthetic or representative data if actual data is not available. Ensure data quality checks are in place.
10. Test methodology:
State transition: to check the transition between power on and power off states.
Equivalence and boundary value: to check the UI, applications(call and dictionary), touch response
Error guessing: to identify potential errors
11. Test approach:
Equivalence and boundary value:
Identify distinct partitions for various functionalities, such as power button behavior and icon display.
Test representative values within each partition to ensure the system behaves as expected.
Specifically apply Boundary Value Analysis to assess the behavior at the edges of identified partitions.
State transition test:
Focus on scenarios involving transitions between different states of the mobile phone, such as power-on and power-off states.
Verify that state transitions occur seamlessly and the system maintains correct behavior in each state.
Error guessing:
Apply the testing team's experience and intuition to identify potential areas of weakness or common sources of errors.
Devise test scenarios based on anticipated error-prone situations, especially in font settings and UI responsiveness.
12. Entry Criteria:
Requirements specification is finalized.
Test environment is set up.
Test data is prepared.
13. Exit criteria:
All test cases executed.
Critical issues resolved.
Acceptance criteria met.
14. Test environments:
We need three or more mobile phones to test and check under various scenarios
All the testing tools
Test data
15. Defect tracking:
Using JIRA, we will raise tickets and will be assigned to the respective developer.
16. Estimation:
Total Estimated Effort: ‘x’ hours per person
Breakdown:
Power On/Off Functionality: ‘x’hours
Icon Display: ‘x’hours
Bottom Bar Icons: ‘x’hours
Contact Display Functionality: ‘x’hours
Dictionary Search Functionality: ‘x’hours
Power Off Confirmation Message: ‘x’hours
Font Settings: ‘x’hours
Touch Responsiveness: ‘x’hours
Absence of Hard Buttons: ‘x’hours
17. Test automation:
Power ON/OFF functionality(buttons), icon display, touch responsiveness need to be tested manually
Dictionary search functionality, font setting, contact display functionality, bottom bar icons can be checked through automation testing
18. Test deliverables :
Test Plan
Test Cases
Test Execution Reports
Defect Reports
Summary Report