Project 1 - V&V SW Analysis - I

Test Plan: Features Testing for New Mobile Phone (Blackbox Test)

1. Introduction:
The purpose of this test plan is to outline the testing approach and test cases for the features of a new mobile phone. The product is still under development and requires thorough testing before User Acceptance Testing (UA). This plan focuses on blackbox testing, where the internal workings of the system are not considered.

2. Test Objectives:
The main objectives of this test plan are:
- To verify that the phone powers on/off correctly.
- To ensure that the icons and apps are displayed properly on the screen.
- To validate the functionality of the "call the phone" and "Dictionary" icons.
- To confirm that the contacts are displayed in chronological order.
- To test the search functionality in the dictionary.
- To verify the font and size settings.
- To ensure the touch responsiveness of the user interface.
- To verify that there are no hard buttons on the mobile phone.

3. Test Environment:
- Mobile phone simulator/emulator
- Test device or simulator/emulator compatible with the mobile phone's operating system
- Test cases management tool
- Bug tracking tool

4. Test Approach:
- The testing will be performed through blackbox testing techniques.
- The focus will be on validating the expected behavior as per the given requirements.
- Both positive and negative test scenarios will be considered.
- Test cases will cover all the identified requirements.

5. Test Scenarios and Test Cases:

Test Scenario 1: Powering On the Phone
Test Case 1.1: Long pressing the power button switches on the phone
- Precondition: Phone is switched off.
- Actions:
1. Long press the power button.
- Expected Result: The phone powers on, and the company logo is displayed at the center of the screen.

Test Scenario 2: Displaying Icons and Apps
Test Case 2.1: Powering on displays all icons in the grid
- Precondition: Phone is switched on.
- Actions:
1. Power on the phone.
- Expected Result: All icons of the apps are present in the grid.

Test Scenario 3: Bottom Bar Icons
Test Case 3.1: "Call the Phone" icon is the first icon in the bottom bar
- Precondition: Phone is powered on.
- Actions:
1. Observe the bottom bar icons.
- Expected Result: The "Call the Phone" icon is the first icon at the bottom bar.

Test Case 3.2: "Dictionary" icon is the second icon in the bottom bar
- Precondition: Phone is powered on.
- Actions:
1. Observe the bottom bar icons.
- Expected Result: The "Dictionary" icon is the second icon at the bottom bar.

Test Scenario 4: Viewing Contacts
Test Case 4.1: Clicking "Call the Phone" icon displays contacts in chronological order
- Precondition: Phone is powered on.
- Actions:
1. Click the "Call the Phone" icon.
- Expected Result: Contacts are visible based on chronological order.

Test Scenario 5: Searching in the Dictionary
Test Case 5.1: Clicking "Dictionary" icon displays a search bar
- Precondition: Phone is powered on.
- Actions:
1. Click the "Dictionary" icon.
- Expected Result: A search bar appears at the middle of the screen.

Test Scenario 6: Powering Off the Phone
Test Case 6.1: Long pressing the power button switches off the phone
- Precondition: Phone is powered on.
- Actions:
1. Long press the power button.
- Expected Result: The phone powers off, and a "Good-Bye" message

is displayed.

Test Scenario 7: Font Settings
Test Case 7.1: Font is always "Calibri (Body)" and size is 12
- Precondition: Phone is powered on.
- Actions:
1. Observe the font settings.
- Expected Result: The font is "Calibri (Body)" and the size is 12 throughout the mobile phone.

Test Scenario 8: UI Touch Responsiveness
Test Case 8.1: UI responds to touch gestures
- Precondition: Phone is powered on.
- Actions:
1. Perform various touch gestures (tap, swipe, pinch, etc.) on the UI elements.
- Expected Result: The UI responds correctly to touch gestures.

Test Scenario 9: Hard Buttons
Test Case 9.1: No hard buttons present on the mobile phone
- Precondition: Phone is powered on.
- Actions:
1. Inspect the mobile phone for any physical buttons.
- Expected Result: There are no hard buttons present on the mobile phone.

6. Test Execution and Reporting:
- Execute the test cases outlined in the test plan.
- Document any defects found during testing in the bug tracking tool.
- Provide a detailed test report with test results, including pass/fail status and any identified issues.

Test plan to test features of a new mobile phone:-

if(owner switch on the phone)
{
company logo at the center of the screen;
}
else if (customer press the power button)
{
open the apps in the grid;
}
else if (owner power on the phone)
{
shows call the phone icon in the first position at the bottom;
}
else if (owner power on the phone)
{
shows Dictionary icon on the second position at the bottom;
}
else if (owner click on call the phone icon)
{
contacts appear in chronological order.
}
else if (owner click on Dictionary icon)
{
the search bar appears at the center;
}
else if (owner long-press power on button)
{
displays Good-Bye and gets switched off;
}
else if (owners phone font)
{
always in caliber with the size of 12;
}
else if (touch-responsive)
{
always need UI to be touch responsive;
}
else (customer required no hard buttons)
{
touch screen sensitive;
}