Project 1 - V&V SW Analysis - I

Test Plan for New Mobile Phone (Blackbox Testing):

_{1. Introduction}

_{This test plan is designed for the black box testing of a new mobile phone, focusing on functional testing based on user stories (US) provided. The product is still in development and has not yet undergone User Acceptance Testing (UAT). The purpose of this test plan is to validate that the phone’s functionalities meet the requirements before release. All hypothetical test data, dependencies, assumptions, and risks will be outlined.}

_{2. Scope}

_{This test plan covers black-box functional testing of the following features:}

• _{Power-on functionality}
• _{Application display and icon grid}
• _{Bottom bar icon functionality}
• _{Contact viewing and dictionary search}
• _{Power-off behavior}
• _{UI font and touch responsiveness}
• _{Removal of hard buttons}

_{3. Features to be Tested}

_{The following features will be tested based on the requirements:}

1. _{Power-On with Company Logo (US-1):}

   • _{The phone should display a company logo when the power button is long pressed.}

2. _{Power-On and App Grid (US-2):}

   • _{After switching on, the phone should display all installed apps in a grid layout.}

3. _{Bottom Bar Icon: "Call the Phone" (US-3):}

   • _{The "Call the Phone" icon should appear first on the bottom bar.}

4. _{Bottom Bar Icon: "Dictionary" (US-4):}

   • _{The "Dictionary" icon should appear second on the bottom bar.}

5. _{Call Icon Functionality (US-5):}

   • _{Clicking on the "Call the Phone" icon should display contacts in chronological order.}

6. _{Dictionary Icon Functionality (US-6):}

   • _{Clicking on the "Dictionary" icon should open a search bar in the middle of the screen.}

7. _{Power-Off with Goodbye Message (US-7):}

   • _{Long pressing the power button should display a "Good-Bye" message and power off the phone.}

8. _{UI Font and Size (US-8):}

   • _{The font should always be "Calibri (Body)" with a size of 12.}

9. _{Touch Responsiveness (US-9):}

   • _{The UI should respond to touch inputs as expected.}

10. _{No Hard Buttons (US-10):}

• _{The phone should not have any hard physical buttons apart from the power button.}

_{4. Test Approach}

_{We will use black box testing to evaluate the system based on its functionality without knowledge of the internal code or system architecture. Testing will focus on:}

• _{Functional Testing: Ensure each feature works as described in the user stories.}
• _{Usability Testing: Validate the ease of use, layout, and responsiveness of the user interface.}
• _{User Acceptance Testing (UAT): Hypothetically prepared to simulate customer interactions with the product.}

5.Test cases

Case ID	Description	Preconditions	Test Steps	Expected Results	Pass/Fail Criteria
TC-01 (US-1)	Verify power-on with company logo	Phone is switched off	1. Long-press the power button.	The phone switches on, and the company logo appears at the center of the screen.	The logo should be clearly displayed, and the phone should power on.
TC-02 (US-2)	Verify power-on displays app grid	Phone is switched off	1. Press the power button to switch on the phone.	The app icons should appear in a grid layout on the home screen.	All apps should be present and correctly aligned in the grid.
TC-03 (US-3)	Verify "Call the Phone" icon is first in the bottom bar	Phone is powered on	1. Observe the bottom bar after powering on the phone.	The "Call the Phone" icon is the first icon in the bottom bar.	The icon should be correctly positioned as the first icon.
TC-04 (US-4)	Verify "Dictionary" icon is second in the bottom bar	Phone is powered on	1. Observe the bottom bar after powering on the phone.	The "Dictionary" icon is the second icon in the bottom bar.	The icon should be correctly positioned as the second icon.
TC-05 (US-5)	Verify contacts display after clicking "Call the Phone"	Phone is powered on, contact list is populated	1. Click the "Call the Phone" icon. 2. Observe the contacts displayed.	Contacts are displayed in chronological order.	All contacts should be visible in the correct order.
TC-06 (US-6)	Verify dictionary search bar appears when clicking "Dictionary" icon	Phone is powered on	1. Click the "Dictionary" icon.	A search bar appears in the center of the screen.	The search bar should be present and functional.
TC-07 (US-7)	Verify power-off displays goodbye message	Phone is powered on	1. Long-press the power button.	The phone displays "Good-Bye" and powers off.	The message should appear, and the phone should power down.
TC-08 (US-8)	Verify default font and size are set to "Calibri (Body)" with size 12	Phone is powered on	1. Observe the font used in the UI.	The font should be "Calibri (Body)" with a size of 12.	Font and size should be consistent across the UI.
TC-09 (US-9)	Verify UI touch responsiveness	Phone is powered on	1. Interact with the UI through touch gestures (e.g., tap, swipe).	The UI responds quickly and accurately to touch inputs.	Touch gestures should be recognized and acted upon promptly.
TC-10 (US-10)	Verify the absence of hard buttons	Phone is powered off or on	1. Physically inspect the phone.	No hard buttons should exist apart from the power button.	There should be no additional hard buttons on the phone.

_{6. Test Deliverables}

_{The following deliverables will be produced:}

• _{Test Plan Document: This document outlining the strategy, scope, and test cases.}
• _{Test Execution Report: A summary of the test execution results (pass/fail status).}
• _{Bug/Defect Report: If any issues are found, a detailed report with reproduction steps will be logged.}
• _{Test Summary Report: An overall evaluation of the phone’s performance, including any deviations from expected behavior.}

_{7. Test Environment}

_{Testing will be conducted on prototype mobile phones. The following components are required:}

• _{Mobile phone device with functional software.}
• _{Charging accessories.}
• _{Simulated contact data for validating the "Call the Phone" functionality.}
• _{Access to a dictionary API (if required for the dictionary functionality).}

_{8. Assumptions and Risks}

_Assumptions:

• _{The phone will have a working operating system.}
• _{All application icons and functionality are pre-installed and ready for testing.}
• _{Testers will have access to a prototype for functional testing.}

_Risks:

• _{Feature changes during development could affect test cases.}
• _{Potential delays in prototype availability may push testing schedules.}
• _{Bugs or incomplete features could hinder full testing before UAT.}

9. Test Schedule

Task	Start Date	End Date
Test Plan Creation	TBD	TBD
Test Case Design and Review	TBD	TBD
Test Environment Setup	TBD	TBD
Test Execution	TBD	TBD
Test Execution Reporting	TBD	TBD
Bug Triage and Fixes	TBD	TBD

_{10. Approval}

_{This test plan is approved by the following stakeholders:}

• _{Product Owner: TBD}
• _{Test Lead: TBD}
• _{Development Lead: TBD}