Project 1 - V&V SW Analysis - I

Test Plan: Mobile Phone Blackbox Testing

1. Introduction:

   • The purpose of this test plan is to verify the functionality and behavior of a new mobile phone.
   • The testing will be conducted from a blackbox perspective, focusing on the external behavior of the phone without considering its internal implementation details.
   • The test plan covers the features and requirements specified in the User Stories (US) provided.

2. Test Objectives:

   • Ensure that the power button long press switches on the phone and displays the company logo at the center of the screen (US-1).
   • Verify that the phone is powered on and all the app icons are present in the grid after pressing the power button (US-2).
   • Confirm that the "call the phone" icon is displayed as the first icon in the bottom bar of the screen after the phone is powered on (US-3).
   • Validate that the "Dictionary" icon is displayed as the second icon in the bottom bar of the screen after the phone is powered 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 in the middle of the screen for word search (US-6).
   • Ensure that long-pressing the power button switches off the phone with a "Good-Bye" message (US-7).
   • Verify that the font in the mobile is "calibri (Body)" and of size 12 (US-8).
   • Validate that the UI is touch responsive (US-9).
   • Confirm that the mobile phone has no hard buttons (US-10).

3. Test Approach:

   • Conduct functional testing to verify the behavior of each feature according to the user stories.
   • Perform blackbox testing without considering the internal implementation details.
   • Use real user scenarios to simulate user interactions with the phone.

4. Test Environment:

   • Hardware: Mobile phone prototype.
   • Software: Mobile operating system (version X.Y.Z).
   • Testing tools: Test management tool, device emulators/simulators, screen recording tools.

5. Test Cases:

   • Develop test cases for each user story, covering positive and negative scenarios.
   • Test cases should include steps to reproduce the expected behavior, input data, and expected outcomes.

6. Test Execution:

   • Execute the test cases based on the test plan and record the results.
   • Log any defects or issues encountered during testing and assign appropriate priorities and severities.
   • Retest the fixed issues to ensure they have been resolved.

7. Test Deliverables:

   • Test plan document.
   • Test cases and test scripts.
   • Test execution results and defect reports.
   • Final test summary report.

8. Risks and Assumptions:

   • Assumption: The mobile phone prototype represents the final product.
   • Risk: Software bugs or hardware issues may impact the expected behavior.
   • Risk Mitigation: Conduct thorough testing, report issues promptly, and involve stakeholders for timely resolutions.

9. Schedule:

   • Define the testing timeline and allocate resources accordingly.
   • Allow sufficient time for test execution, defect management, and retesting.

10. Exit Criteria:

    • All test cases have been executed and their results recorded.
    • Critical defects have been fixed and retested.
    • Test summary report has been reviewed and approved.