Project 1 - V&V SW Analysis - I
Note: Please use the below attached PDF for better readability
Write a Test plan to test features of a new mobile phone (Blackbox test) that needs to be implemented based on the following requirements. (The product is still under development stage and is yet to be UA (User Acceptance ) tested . Every other thing to be included in the test plan can be hypothetical.
Aim: Write a Test plan to test the features of a new mobile phone.
Black box testing:
Black box testing is a technique of software testing that examines the functionality of the software without peering into its internal structure or coding. The primary source of black-box testing is a specification of requirements that is stated by the customer.
In this method, the tester selects a function gives input value to examine its functionality, and checks whether the function is giving the expected output or not. If the function produces the correct output, then it is passed in testing, otherwise failed. The test team reports the result to the development team and then tests the next function. After completing the testing of all functions if there are severe problems, then it is given back to the development team for correction.
What is the Test Plan:
A Test Plan is a document that consists of all future testing-related activities. It is prepared at the project level and in general, it defines work products to be tested, how they will be tested, and test type distribution among the testers. Before starting testing there will be a test manager who will be preparing a test plan. In any company whenever a new project is taken up before the tester involves in the testing the test manager of the team would prepare a test Plan.
Test Plan: New Mobile Phone Feature Testing (Blackbox)
<!-- [if !supportLists]-->1. <!--[endif]-->Objective:
<!-- [if !supportLists]-->To verify and validate the functionality of the new mobile phone according to the provided specifications.
<!-- [if !supportLists]-->To ensure that the mobile phone operates correctly and meets customer expectations.
<!-- [if !supportLists]-->2. <!--[endif]-->Scope:
In-scope:
<!-- [if !supportLists]-->Powering on the phone (owner and customer scenarios).
<!-- [if !supportLists]-->Displaying company logo.
<!--[endif]-->Launching apps from the grid.
<!-- [if !supportLists]-->Displaying phone and dictionary icons.
<!-- [if !supportLists]-->Navigating to contacts and search functionalities.
<!-- [if !supportLists]-->Powering off the phone.
<!-- [if !supportLists]-->Font size and touch responsiveness.
Out-of-scope:
<!-- [if !supportLists]-->Detailed testing of individual apps.
<!-- [if !supportLists]-->Hardware-specific testing (e.g., camera, sensors).
<!-- [if !supportLists]-->3. <!--[endif]-->Test Approach:
<!-- [if !supportLists]-->Black box testing will be used to evaluate the mobile phone's features.
<!-- [if !supportLists]-->Functional testing will be performed based on the specified requirements and user scenarios.
<!-- [if !supportLists]-->4. <!--[endif]-->Testing Methodology:
<!-- [if !supportLists]-->Functional testing, including positive and negative test cases.
<!-- [if !supportLists]-->User scenario-based testing.
<!-- [if !supportLists]-->5. <!--[endif]-->Test Environment:
Hardware Configuration:
<!-- [if !supportLists]-->Various mobile devices for testing.
Software Configuration:
<!-- [if !supportLists]-->Operating systems (e.g., Android, iOS).
Installation of Software:
<!-- [if !supportLists]-->Verification of app installation and uninstallation.
<!-- [if !supportLists]-->6. <!--[endif]-->Assumptions:
<!-- [if !supportLists]-->Proper support from the development team.
<!-- [if !supportLists]-->Adequate knowledge transfer from the development team.
<!-- [if !supportLists]-->Resource allocation as per project requirements.
<!-- [if !supportLists]-->7. <!--[endif]-->Risks:
<!-- [if !supportLists]-->Test Manager's management skills.
<!-- [if !supportLists]-->Project timeline and completion.
<!-- [if !supportLists]-->Team cooperation and communication.
<!-- [if !supportLists]-->8. <!--[endif]-->Roles and Responsibilities:
Test Manager: Overall project management, resource allocation, and direction.
Testers: Test case identification, verification of test approach, and cost management.
<!-- [if !supportLists]-->9. <!--[endif]-->Test Schedule:
<!-- [if !supportLists]-->Testing will commence as soon as the product is available for testing.
<!-- [if !supportLists]-->10. <!--[endif]-->Entry and Exit Criteria:
Entry Criteria:
<!-- [if !supportLists]-->Necessary resources are available.
<!-- [if !supportLists]-->The mobile phone is prepared for testing.
<!-- [if !supportLists]-->Test data is ready.
Exit Criteria:
<!-- [if !supportLists]-->No critical bugs exist.
<!-- [if !supportLists]-->Most test cases have passed.
<!-- [if !supportLists]-->All planned test cases have been executed.
<!-- [if !supportLists]-->10. <!--[endif]-->Test Automation:
<!-- [if !supportLists]-->Features with frequent testing may be automated, while others will be manually tested.
<!-- [if !supportLists]-->11. <!--[endif]-->Deliverables:
Before Testing Phase:
<!-- [if !supportLists]-->Test plan document.
<!-- [if !supportLists]-->Test case document.
<!-- [if !supportLists]-->Test design specification.
<!-- [if !supportLists]-->During Testing Phase:
<!-- [if !supportLists]-->Test scripts.
<!-- [if !supportLists]-->Test data.
<!-- [if !supportLists]-->Error logs.
After Testing Phase:
<!-- [if !supportLists]-->Test reports.
<!-- [if !supportLists]-->Defect reports.
<!-- [if !supportLists]-->Installation report.
<!-- [if !supportLists]-->12. <!--[endif]-->Test Features and Scenarios:
US-1: Power On with Company Logo
Test Case 1: Long-press power button.
Expected Result: Phone powers on with the company logo displayed at the center of the screen.
US-2: App Icons Grid
Test Case 2: Press power button.
Expected Result: Phone powers on, and all app icons are visible in a grid.
US-3: "Call the Phone" Icon
Test Case 3: Power on the phone.
Expected Result: The "Call the Phone" icon should be the first icon on the bottom bar.
US-4: "Dictionary" Icon
Test Case 4: Power on the phone.
Expected Result: The "Dictionary" icon should be the second icon on the bottom bar.
US-5: Contacts Display
Test Case 5: Click "Call the Phone" icon.
Expected Result: All contacts should be visible in chronological order.
US-6: Dictionary Search
Test Case 6: Click "Dictionary" icon.
Expected Result: A search bar should appear at the middle of the screen for word search.
US-7: Power Off with "Good-Bye" Message
Test Case 7: Long-press power button.
Expected Result: The phone should power off, displaying a "Good-Bye" message.
US-8: Font Settings
Test Case 8: Check the font settings.
Expected Result: The font should always be "Calibri (Body)" with a size of 12.
US-9: Touch Responsiveness
Test Case 9: Use various touch interactions on the UI.
Expected Result: The UI should respond accurately and swiftly to touch input.
US-10: No Hard Buttons
Test Case 10: Inspect the physical phone.
Expected Result: The mobile phone should have no hard buttons.
Test plan to test features of a new mobile phone:-
here's a simplified C program structure based on the provided requirements:
#include
void display_company_logo_at_center()
{
// Display the company logo at the center of the screen
printf("Company logo displayed at the center\n");
}
void open_apps_in_grid()
{
// Open apps in a grid
printf("Apps opened in a grid\n");
}
void show_call_the_phone_icon_in_first_position()
{
// Show "Call the Phone" icon in the first position at the bottom
printf("Call the Phone icon shown at the first position\n");
}
void show_dictionary_icon_in_second_position()
{
// Show "Dictionary" icon in the second position at the bottom
printf("Dictionary icon shown at the second position\n");
}
void display_contacts_in_chronological_order()
{
// Display contacts in chronological order
printf("Contacts displayed in chronological order\n");
}
void display_search_bar_at_center()
{
// Display a search bar at the center of the screen
printf("Search bar displayed at the center\n");
}
void display_goodbye_message_and_switch_off()
{
// Display "Good-Bye" message and switch off
printf("Good-Bye message displayed, phone switched off\n");
}
void set_font_to_calibri_with_size_12()
{
// Set the phone font to Calibri with size 12
printf("Font set to Calibri with size 12\n");
}
void ensure_touch_ui_responsiveness()
{
// Ensure that the UI is touch responsive
printf("UI is touch responsive\n");
}
void ensure_no_hard_buttons()
{
// Ensure that there are no hard buttons (touch screen sensitive)
printf("No hard buttons, touch screen is sensitive\n");
}
int main()
{
// Simulate the phone behavior based on the conditions
int owner_switches_on_phone = 0;
int customer_presses_power_button = 1;
int owner_powers_on_phone = 0;
int owner_clicks_on_call_the_phone_icon = 0;
int owner_clicks_on_dictionary_icon = 0;
int owner_long_presses_power_on_button = 0;
int owner_phone_font = 0;
int touch_responsive = 1;
if (owner_switches_on_phone)
{
display_company_logo_at_center();
}
else if (customer_presses_power_button)
{
open_apps_in_grid();
}
else if (owner_powers_on_phone)
{
show_call_the_phone_icon_in_first_position();
}
else if (owner_powers_on_phone)
{
show_dictionary_icon_in_second_position();
}
else if (owner_clicks_on_call_the_phone_icon)
{
display_contacts_in_chronological_order();
}
else if (owner_clicks_on_dictionary_icon)
{
display_search_bar_at_center();
}
else if (owner_long_presses_power_on_button)
{
display_goodbye_message_and_switch_off();
}
else if (owner_phone_font)
{
set_font_to_calibri_with_size_12();
}
else if (touch_responsive)
{
ensure_touch_ui_responsiveness();
}
else {
ensure_no_hard_buttons();
}
return 0;
}
Please note: that this C program is a simplified representation and does not handle user input or provide a complete user interface. It serves as a basic structure to demonstrate how the requirements can be implemented using functions and conditional statements in C.
Conclusion:
This test plan outlines the testing approach for the new mobile phone's features. Successful testing will ensure that the product meets user expectations and functions as intended.