Project 1 - V&V SW Analysis - I

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 is 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, 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.

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.
• It determines the time, cost, and effort.
• Provide a schedule for testing activities.
• Resource requirement 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,

1. Objective: It describes the aim of the test plan, whatever the good process and procedure they are going to follow in order to give quality software to customers. The overall objective of the test is to find as many defects as possible and to make software bug free. The test objective must be broken into components and sub-components.

2. 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.

3. 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.

4. Approach: The approach of testing different software is different. It deals with the flow of applications for future references.

5. 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.

6. Risk: All the risks that can happen if the assumption is breaking. For Example, in the case of wrong budget estimation, the cost may overrun. Some reason that may lead to risk is:

   • Test Manager has poor management skills.
   • Hard to complete the project on time.
   • Lack of cooperation.

7. 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 risk:

   • Test priority is to be set for each test activity.
   • Managers should have leadership skills.
   • Training course for the testers.

8. 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 each and every testing-related activity. For Example, writing test case date and ending test case date.
10. Defect Tracking: 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 which the testing team will use i.e. 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.

12. Entry and Exit Criteria: The set of conditions that should be met in order 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.

13. 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.

14. 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 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;
}

Test Plan: Blackbox Testing for New Mobile Phone

1. Introduction:

   • Purpose: The purpose of this test plan is to outline the testing approach for the new mobile phone's features based on the provided requirements.
   • Objectives: The objectives of this testing are to ensure that the phone's features are implemented correctly, the user interface is functional and responsive, and the expected behavior is met.

2. Scope:

   • This test plan focuses on blackbox testing, where the internal implementation details of the phone are not known.
   • The testing will cover the features specified in the user stories (US) 1 to 10.

3. Test Environment:

   • Hardware: The test environment will include the new mobile phone hardware.
   • Software: The phone's software, including the operating system and applications, will be included.

4. Test Strategy:

   • The test strategy will involve conducting functional testing to verify that the features of the new mobile phone work according to the provided requirements.
   • The focus will be on blackbox testing techniques, where the internal workings of the phone will not be considered.

5. Test Cases:

   • Test Case 1: Power Button Long Press (US-1)

     • Description: Verify that when the power button is long-pressed, the phone switches on and displays the company logo in the center of the screen.
     • Expected Result: The phone should switch on and display the company logo as specified.

   • Test Case 2: Power Button Press (US-2)

     • Description: Verify that pressing the power button switches on the phone and displays all the application icons in the grid.
     • Expected Result: The phone should switch on and show all the application icons in the grid.

   • Test Case 3: Bottom Bar Icons (US-3, US-4)

     • Description: Verify that after powering on the phone, the "Call the phone" icon is the first icon and the "Dictionary" icon is the second icon on the bottom bar of the screen.
     • Expected Result: The "Call the phone" icon should be the first icon and the "Dictionary" icon should be the second icon on the bottom bar of the screen.

   • Test Case 4: Contact List (US-5)

     • Description: Verify that clicking on the "Call the phone" icon displays all the contacts in chronological order.
     • Expected Result: Clicking on the "Call the phone" icon should display all the contacts in chronological order.

   • Test Case 5: Dictionary Search (US-6)

     • Description: Verify that clicking on the "Dictionary" icon displays a search bar in the middle of the screen for searching word meanings.
     • Expected Result: Clicking on the "Dictionary" icon should display a search bar for searching word meanings.

   • Test Case 6: Power Button Long Press (US-7)

     • Description: Verify that long-pressing the power button switches off the phone and displays a "Goodbye" message.
     • Expected Result: Long-pressing the power button should switch off the phone and display a "Goodbye" message.

   • Test Case 7: Font and Size (US-8)

     • Description: Verify that the font in the mobile is always "Calibri (Body)" and of size 12.
     • Expected Result: The font in the mobile should always be "Calibri (Body)" and of size 12.

   • Test Case 8: UI Touch Responsiveness (US-9)

     • Description: Verify that the user interface of the phone is touch responsive.
     • Expected Result: The user interface should respond accurately and quickly to touch interactions.

   • Test Case 9: No Hard Buttons (US-10)

     • Description: Verify that the mobile phone has no hard buttons.
     • Expected Result: The mobile phone should not have any physical buttons.

6. Test Execution:

   • Execute the test cases outlined in the previous section.
   • Record the actual results and any deviations from the expected results.
   • Report any defects found during the testing process.

7. Test Deliverables:

   • Test plan document.
   • Test execution report.
   • Defect reports, if any.

8. Test Schedule:

   • Define the estimated time required to execute the test cases.
   • Allocate resources and plan the testing activities accordingly.

9. Risks and Assumptions:

   • Risks: Potential risks may include hardware or software malfunctions, compatibility issues, or unexpected behaviors.
   • Assumptions: The assumption is that the development of the mobile phone's features is complete and ready for testing.

10. Test Closure:

    • Once testing is completed, perform a final review of the test results and ensure that all the requirements are met.
    • Prepare the final test report summarizing the testing activities, results, and any outstanding issues.