Project 1 - V&V SW Analysis - I
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.
MOBILE PHONE TEST PLAN.
Introduction
This test plan outlines the testing approach for a new mobile phone currently under development. The focus of this plan is to perform blackbox testing to ensure the product meets the specified requirements. The testing is performed from a user's perspective without knowledge of the internal implementation. The mobile phone is in the development stage and has not undergone User Acceptance Testing (UAT).
Objective
The objective of this test plan is to verify that the mobile phone meets the specified requirements (User Stories) and functions correctly.
Scope
This test plan covers the testing of the following User Stories (US) for the mobile phone:
1. US-1: Power On and Display Company Logo
2. US-2: Display App Icons after Powering On
3. US-3: "Call the Phone" Icon Placement
4. US-4: "Dictionary" Icon Placement
5. US-5: Viewing Contacts upon Clicking "Call the Phone" Icon
6. US-6: Searching for Word Meanings with the "Dictionary" Icon
7. US-7: Power Off with "Good-Bye" Message
8. US-8: Font Style and Size
9. US-9: Touch Responsiveness
10. US-10: No Hard Buttons
Test Environment
- Mobile phone hardware and software in the development stage.
Test Approach
Blackbox testing will be performed without knowledge of the internal system design. Testing will be carried out through interaction with the mobile phone's user interface.
Test Scenarios
US-1: Power On and Display Company Logo
- Test Scenario 1: Long-press power button, verify the phone switches on, and the company logo is displayed in the center of the screen.
US-2: Display App Icons after Powering On
- Test Scenario 2: Press power button, verify that all app icons are displayed in a grid on the screen.
US-3: "Call the Phone" Icon Placement
- Test Scenario 3: Power on the phone, check that the "Call the Phone" icon is the first icon at the bottom bar of the screen.
US-4: "Dictionary" Icon Placement
- Test Scenario 4: Power on the phone, check that the "Dictionary" icon is the second icon at the bottom bar of the screen.
US-5: Viewing Contacts upon Clicking "Call the Phone" Icon
- Test Scenario 5: Click the "Call the Phone" icon, and verify that all contacts are visible in chronological order.
US-6: Searching for Word Meanings with the "Dictionary" Icon
- Test Scenario 6: Click the "Dictionary" icon and verify that a search bar appears in the middle of the screen for searching word meanings.
US-7: Power Off with "Good-Bye" Message
- Test Scenario 7: Long-press the power button to switch off the phone, and verify that a "Good-Bye" message is displayed.
US-8: Font Style and Size
- Test Scenario 8: Check the font style on the mobile, ensure it is "Calibri (Body)," and the font size is 12.
US-9: Touch Responsiveness
- Test Scenario 9: Test the touch responsiveness of the UI by interacting with the screen to ensure smooth and accurate touch response.
US-10: No Hard Buttons
- Test Scenario 10: Physically inspect the mobile phone to ensure it has no hard buttons as per the requirement.
Test Execution
Testing will be carried out by a dedicated QA team. Test cases will be executed as per the test scenarios outlined in this plan. Defects, if found, will be reported to the development team for resolution.
Test Deliverables
- Test case results, including pass/fail status and any defects found.
- Test summary report.
Test Schedule
The testing will commence upon the availability of the development build and will be conducted over a specified period based on the project timeline.
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 which 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 are stated by the customer
In this method, the tester selects a function and 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 they 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
Importance of Test Plan:
The following are some of the key benefits of making a test plan
It acts as a quick guide for the testing process
It helps to avoid out-of-scope functionalities
determines the time, cost, and effort
Provide a schedule for testing activities Resource requirements and equipment
Test Plan Document can be used for similar projects
It helps to understand the test details
It helps in determining the quality of software applications
Test Plan Attributes:
There some 15 attributes in Test Plan as follow
Objective: it describes the aim of the test plan, whatever the good process and procedure they are going to follow to give quality software to customers. The overall objective of the test is to find as many defects as possible and to make software bugs free the test objective must be broken into components and sub-components.
Test Strategy: it is a crucial document that is to be performed and usually designed by the Test Manager, it helps to determine Test Effort and Test cost. Test strategy helps to determine the features that are going to be tested and the features that will not be tested. The scope can be divided into two parts:
In-Scope: The modules that are to be tested rigorously
Out-Scope: The modules that are not to be tested rigorously
Testing Methodology: The methods that are going to be used for testing depend on application to application. The testing methodology is decided based on the feature and application requirements. Since the testing terms are not standard, one should define what kind of testing will be used in the testing methodology. So that everyone can understand it
Approach: The approach to testing different software is different it deals with the flow of applications for future references.
Assumptions: in this phase, certain assumptions will be made.
Example:
The testing team will get proper support from the development team.
The tester will get proper knowledge transfer from the development team
Proper resource allocation will be given by the company to the testing department
Risk: All the risks that can happen if the assumption is breaking For Example, in the case of a wrong budget destination, the cost may overrun. Some reasons that may lead to risk in
Test Manager has poor management skills.
Hard to complete the project on time.
Lack of cooperation.
Backup/Mitigation Plan- if any risk is involved then the company must have a backup plan the purpose is to avoid errors. Some points to resolve/avoid the risk
Test priority is to be set for each test activity.
Managers should have leadership skills.
Training course for the testers.
Roles and Responsibilities: All the responsibilities and role of every member in a particular testing team has to be recorded.
Example:
Test Manager: Manages the project, takes an appropriate resource, and gives project direction.
Tester: identify the testing technique, verify the test approach, and save project cost.
9. Scheduling: Under this, it will record the start and the end date of every testing-related activity.
For example, Writing the test case date and ending the test case date.
10. Defect Trading: it is an important process in software engineering as lots of issue arises when you develop a critical system for business. If there is any defect found while testing and that defect must be given to the developer team.
11. Test Environment-It is the environment in which the testing team will use Le the list of hardware and software, while testing the application, the things which are said to be tested will be written under this section. The installation of software is also checked under this.
Example:
Software configuration on different operating systems, such as Windows, Linux, Mac, etc.
Hardware Configuration depends on RAM, ROM, etc.
Entry and Exit Criteria: The set of conditions that should be met to start any new type of testing or to end any kind of testing.
Entry Condition:
Necessary resources must be ready.
The application must be prepared
Test data should be ready.
Exit Condition:
There should not be any major bug
Most test cases should be passed.
When all test cases are executed.
Test Automation: It consists of the features that are to be automated and which features are not to be automated.
If the feature has lots of bugs then it is categorized as Manual Testing.
If the feature is frequently tested then it can be automated.
Deliverables- It is the outcome from the testing team and that is to be given to the customers at the end of the project.
Before the testing phase:
Test plan document.
Test case document
Test design specification
During the testing phase
Test scripts
Test data
Error logs
After the testing phase
Test Reports
Defect Report
Installation Report
Test plan to test features of a new mobile phone:
If (owner switches 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 clicks 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;
}