Project 1 - V&V SW Analysis - I
Test Plan for New Mobile Phone Features (Blackbox Testing)
-
Introduction:
- The purpose of this test plan is to verify the functionality of the new mobile phone based on the provided requirements.
- This is a blackbox testing approach where the internal workings of the phone are not considered, and only the expected user behavior is tested.
- The focus is on ensuring that the specified features work as intended and meet the user's expectations.
-
Test Objectives:
- Verify that the power button long press switches on the phone with the company logo displayed at the center of the screen (US-1).
- Verify that all the icons of the apps are present in the grid upon powering on the phone (US-2).
- Verify that the "call the phone" icon appears as the first icon at the bottom bar of the screen after powering on (US-3).
- Verify that the "Dictionary" icon appears as the second icon at the bottom bar of the screen after powering on (US-4).
- Verify that clicking the "call the phone" icon displays all the contacts in chronological order (US-5).
- Verify that clicking the "Dictionary" icon displays a search bar to search for word meanings (US-6).
- Verify that long-pressing the power button switches off the phone with a "Good-Bye" message displayed (US-7).
- Verify that the font in the mobile is always "calibri (Body)" with a size of 12 (US-8).
- Verify that the UI of the mobile phone is touch-responsive (US-9).
- Verify that the mobile phone has no hard buttons (US-10).
-
Test Approach:
- Perform manual testing using a test device or simulator.
- Use test cases to validate the expected behavior of each feature.
- Perform functional testing, UI testing, and usability testing to ensure the phone meets user expectations.
- Use exploratory testing techniques to identify any additional issues or unexpected behavior.
-
Test Cases:
a) Power On and Logo Display (US-1):
- Precondition: Phone is switched off.
- Test Steps:
- Long press the power button.
- Observe the screen for the company logo at the center.
- Expected Result: The phone switches on and the company logo is displayed.
b) App Icons in the Grid (US-2):
- Precondition: Phone is switched on.
- Test Steps:
- Power on the phone.
- Verify that all the app icons are present in the grid.
- Expected Result: All the app icons are displayed in the grid.
c) "Call the Phone" Icon Position (US-3):
- Precondition: Phone is switched on.
- Test Steps:
- Power on the phone.
- Verify that the "call the phone" icon is positioned as the first icon at the bottom bar.
- Expected Result: The "call the phone" icon is the first icon at the bottom bar.
d) "Dictionary" Icon Position (US-4):
- Precondition: Phone is switched on.
- Test Steps:
- Power on the phone.
- Verify that the "Dictionary" icon is positioned as the second icon at the bottom bar.
- Expected Result: The "Dictionary" icon is the second icon at the bottom bar.
e) Contacts Display (US-5): -
Precondition: Phone is switched on.
- Test Steps:
1. Click the "call the phone" icon.
2. Verify that all the contacts are visible.
3. Check if the contacts are displayed in chronological order.
- Expected Result: All contacts are visible, and they are displayed in chronological order.
f) Dictionary Search Bar (US-6):
- Precondition: Phone is switched on.
- Test Steps:
1. Click the "Dictionary" icon.
2. Verify that a search bar appears at the middle of the screen.
3. Attempt to search for a word and observe the results.
- Expected Result: The search bar appears, allowing the user to search for word meanings, and relevant results are displayed.
g) Power Off and "Good-Bye" Message (US-7):
- Precondition: Phone is switched on.
- Test Steps:
1. Long press the power button.
2. Verify that the phone switches off.
3. Check if a "Good-Bye" message is displayed.
- Expected Result: The phone is switched off, and a "Good-Bye" message is displayed.
h) Font and Size (US-8):
- Precondition: Phone is switched on.
- Test Steps:
1. Verify the font in different areas of the mobile phone, such as menus, messages, etc.
2. Check the font size throughout the UI.
- Expected Result: The font used in the mobile phone is "calibri (Body)" with a size of 12.
i) UI Touch Responsiveness (US-9):
- Precondition: Phone is switched on.
- Test Steps:
1. Perform various touch actions on the UI, such as tapping, swiping, and scrolling.
2. Observe the responsiveness and accuracy of the touch inputs.
- Expected Result: The UI of the mobile phone responds accurately and promptly to touch inputs.
j) Absence of Hard Buttons (US-10):
- Precondition: Phone is switched on.
- Test Steps:
1. Inspect the physical design of the phone.
2. Verify that there are no hard buttons present on the phone.
- Expected Result: The mobile phone does not have any hard buttons.
-
Test Environment:
- Specify the hardware and software environment required for testing, including the test device or simulator, operating system, and any additional tools.
-
Test Schedule:
- Define the estimated start and end dates for testing each feature based on the development timeline.
-
Test Deliverables:
- Specify the test deliverables, such as test reports, bug reports, and any other documentation required.
-
Test Risks and Mitigation:
- Identify potential risks, such as compatibility issues, performance limitations, or resource constraints, and propose mitigation strategies.
-
Test Dependencies:
- Specify any dependencies on external factors or components, such as network connectivity or third-party integrations.
-
Test Execution:
- Assign responsibilities for test execution and ensure that the necessary resources are available.
-
Bug Reporting:
- Define the bug reporting process, including the required information and format for reporting bugs encountered during testing.
-
Test Completion Criteria:
- Specify the criteria that must be met to consider the testing phase complete, such as the successful execution of all test cases and the resolution of critical bugs.