Project 1 - V&V SW Analysis - I
Introduction
This test plan outlines the testing strategy for evaluating the features of a new mobile phone currently under development. The purpose of this test plan is to ensure that the phone's functionality meets the specified requirements and that it performs as expected before user acceptance testing (UA).
Objectives
The objectives of this test plan are as follows:
- Verify that the mobile phone meets the defined user stories (US).
- Identify and report any defects or issues.
- Ensure that the user interface (UI) is touch-responsive and intuitive.
- Confirm that the phone does not have any hard buttons.
- Ensure consistent font settings throughout the phone's UI.
Scope
The scope of this test plan includes the following areas:
- Power button functionality (US-1, US-7)
- App icons on the home screen (US-2, US-3, US-4)
- Contact list display (US-5)
- Dictionary search feature (US-6)
- Font settings (US-8)
- Touch responsiveness (US-9)
- Absence of hard buttons (US-10)
-
Test Cases
Power Button Functionality
Test Case 1: Power On
-
Test Steps:
- Long-press the power button.
- Observe the screen for a company logo at the center.
-
Expected Result: The phone switches on with the company logo displayed as specified in US-1.
Test Case 2: Power Off
-
Test Steps:
- Long-press the power button.
- Observe the screen for the "Good-Bye" message.
-
Expected Result: The phone switches off, displaying the "Good-Bye" message as specified in US-7.
-
Home Screen Icons
Test Case 3: App Icons
-
Test Steps:
- Power on the phone.
- Check if all the app icons are present in the grid on the home screen.
-
Expected Result: All app icons are displayed on the home screen as specified in US-2, US-3, and US-4.
Contact List
Test Case 4: Contact Display
-
Test Steps:
- Power on the phone.
- Click the "call the phone" icon.
- Check if all contacts are visible in chronological order.
-
Expected Result: All contacts are visible in chronological order as specified in US-5.
Dictionary Search
Test Case 5: Dictionary Search
-
Test Steps:
- Power on the phone.
- Click the "Dictionary" icon.
- Check if a search bar appears at the middle of the screen.
-
Expected Result: A search bar appears in the middle of the screen as specified in US-6.
Font Settings
Test Case 6: Font Verification
-
Test Steps:
- Power on the phone.
- Navigate through various screens and apps.
- Check if the font is consistently "Calibri (Body)" and size 12 as specified in US-8.
-
Expected Result: The font is consistently "Calibri (Body)" and size 12 throughout the UI.
Touch Responsiveness
Test Case 7: UI Touch Responsiveness
-
Test Steps:
- Power on the phone.
- Interact with the UI by tapping and swiping on different areas of the screen.
-
Expected Result: The UI responds promptly and accurately to touch gestures, meeting the touch responsiveness requirement (US-9).
Absence of Hard Buttons
Test Case 8: Hard Buttons Verification
-
Test Steps:
- Physically inspect the mobile phone for any hard buttons.
-
Expected Result: The mobile phone does not have any hard buttons, as specified in US-10.
Conclusion
This test plan outlines a comprehensive testing strategy to evaluate the features and functionality of the new mobile phone based on the defined user stories. It aims to identify and report any issues, ensuring that the phone meets the specified requirements and is ready for user acceptance testing. Once the testing is complete, any defects found should be documented and addressed before proceeding with further development or UA testing.