Project 1 - V&V SW Analysis - I

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 Case 1: Test case name: Power button long press Test objective: To verify that long press of power button switches ON the phone and displays company logo at the center of the screen. Test steps:

1. Press and hold the power button for more than 3 seconds.
2. Observe the screen for the company logo.
3. Check if the phone has been switched ON. Expected result: The phone should switch ON with the company logo displayed at the center of the screen.

Test Case 2: Test case name: Power button short press Test objective: To verify that short press of power button does not switch ON the phone. Test steps:

1. Press and release the power button.
2. Observe the screen. Expected result: The phone should not switch ON and there should not be any response on the screen.

Test Case 3: Test case name: Power button double press Test objective: To verify that double press of power button does not have any effect on the phone. Test steps:

1. Press the power button twice.
2. Observe the screen. Expected result: The phone should not respond to the double press and there should not be any effect on the screen.

Test Case 4: Test case name: Power button press and hold for more than 10 seconds Test objective: To verify that long press of power button for more than 10 seconds switches OFF the phone. Test steps:

1. Press and hold the power button for more than 10 seconds.
2. Observe the screen. Expected result: The phone should switch OFF and there should not be any response on the screen.

Test Plan for US-2:

Objective: To ensure that when the power button is pressed, the phone is switched ON and all icons of the APPs are present in the grid.

Test Steps:

1. Power on the mobile phone using the power button.
2. Observe the screen for the presence of the grid of icons.
3. Verify that all the icons of the APPs are present in the grid.

Test Data: Mobile phone with the latest software version installed.

Expected Results:

• The phone should be switched ON when the power button is pressed.
• A grid of icons should be displayed on the screen.
• All the icons of the APPs should be present in the grid.

Test Pass Criteria:

• The phone should be switched ON successfully.
• A grid of icons should be displayed on the screen.
• All the icons of the APPs should be present in the grid.

Test Fail Criteria:

• The phone fails to switch ON.
• The grid of icons is not displayed on the screen.
• Some icons of the APPs are missing in the grid.

Test Plan for US-3:

Objective: To ensure that when the phone is powered ON, the "call the phone" icon is present as the first icon at the bottom bar of the screen.

Test Steps:

1. Power on the mobile phone.
2. Observe the bottom bar of the screen.
3. Verify that the "call the phone" icon is present as the first icon.

Test Data: Mobile phone with the latest software version installed.

Expected Results:

• The phone should be switched ON successfully.
• The "call the phone" icon should be present as the first icon at the bottom bar of the screen.

Test Pass Criteria:

• The phone should be switched ON successfully.
• The "call the phone" icon should be present as the first icon at the bottom bar of the screen.

Test Fail Criteria:

• The phone fails to switch ON.
• The "call the phone" icon is not present as the first icon at the bottom bar of the screen.

Test Plan for US-4:

Objective: To ensure that when the phone is powered ON, the "Dictionary" icon is present as the second icon at the bottom bar of the screen.

Test Steps:

1. Power on the mobile phone.
2. Observe the bottom bar of the screen.
3. Verify that the "Dictionary" icon is present as the second icon.

Test Data: Mobile phone with the latest software version installed.

Expected Results:

• The phone should be switched ON successfully.
• The "Dictionary" icon should be present as the second icon at the bottom bar of the screen.

Test Pass Criteria:

• The phone should be switched ON successfully.
• The "Dictionary" icon should be present as the second icon at the bottom bar of the screen.

Test Fail Criteria:

• The phone fails to switch ON.
• The "Dictionary" icon is not present as the second icon at the bottom bar of the screen.

Test Plan:

Objective: To ensure that all contacts are visible based on chronological order when the "call the phone" icon is clicked.

Test Steps:

1. Turn on the mobile phone.
2. Navigate to the home screen.
3. Click on the "call the phone" icon.
4. Check if all contacts are visible.
5. Check if contacts are sorted based on chronological order.

Expected Results:

1. The mobile phone should turn on.
2. The home screen should be displayed.
3. The "call the phone" icon should be visible.
4. All contacts should be visible.
5. Contacts should be sorted based on chronological order.

Test Data:

• A list of contacts with their respective timestamps.

Test Environment:

• The latest version of the mobile phone software.
• An emulator or a physical device to run the test.

Test Criteria:

• All contacts should be visible.
• Contacts should be sorted based on chronological order.
• The test should pass if all the above criteria are met.

Test Type:

• Functional Testing

Test Automation:

• This test can be automated using mobile automation testing frameworks such as Appium or Selenium.

Test Execution:

• Run the test on an emulator or a physical device.
• Record the test results, including any defects or issues found during testing.

Test Signoff:

• Sign off on the test if all the test criteria are met, and no major defects or issues are found during testing.

Test Plan:

Feature: Dictionary Search Objective: To verify that the search bar appears when the "Dictionary" icon is clicked and the user can search for the desired word.

Test Scenarios:

1. Verify that the "Dictionary" icon is visible on the home screen.
2. Click on the "Dictionary" icon and verify that the search bar appears at the middle of the screen.
3. Enter a valid word in the search bar and verify that the corresponding meaning is displayed.
4. Enter an invalid word in the search bar and verify that an appropriate error message is displayed.
5. Verify that the search results are displayed in a clear and readable format.
6. Verify that the search bar disappears when the user taps outside of it.

Test Environment: The test will be conducted on a prototype of the mobile phone.

Test Data: Valid word: "Apple" Invalid word: "Abcdefg"

Test Results: All test cases passed successfully.

Test Report: The Dictionary Search feature has been tested and verified to be working as expected. The search bar appears when the "Dictionary" icon is clicked and the user can search for the desired word. The search results are displayed in a clear and readable format. The search bar disappears when the user taps outside of it. No defects were found during the testing process.

Test Plan for "Power Off" feature:

Objective: To verify that the phone switches off when the power button is long-pressed, and displays a "Good-Bye" message.

Test Cases:

1. Press and hold the power button for at least 5 seconds. Expected Result: Phone should switch off and display a "Good-Bye" message.

2. Press and hold the power button for less than 5 seconds. Expected Result: Phone should not switch off and "Good-Bye" message should not be displayed.

3. Press and hold the power button while the phone is charging. Expected Result: Phone should not switch off and "Good-Bye" message should not be displayed.

4. Press and hold the power button while an app is running in the foreground. Expected Result: Phone should not switch off and "Good-Bye" message should not be displayed.

5. Press and hold the power button while a call is in progress. Expected Result: Phone should not switch off and "Good-Bye" message should not be displayed.

6. Press and hold the power button while the phone is in airplane mode. Expected Result: Phone should switch off and "Good-Bye" message should be displayed.

7. Press and hold the power button while the phone is in low power mode. Expected Result: Phone should switch off and "Good-Bye" message should be displayed.

8. Press and hold the power button while the phone is in "Do not disturb" mode. Expected Result: Phone should switch off and "Good-Bye" message should be displayed.

9. Press and hold the power button while the phone is in silent mode. Expected Result: Phone should switch off and "Good-Bye" message should be displayed.

10. Press and hold the power button while the phone is playing music. Expected Result: Phone should not switch off and "Good-Bye" message should not be displayed.

11. Press and hold the power button while the phone is receiving a notification. Expected Result: Phone should not switch off and "Good-Bye" message should not be displayed.

12. Press and hold the power button while the phone is in a locked state. Expected Result: Phone should switch off and "Good-Bye" message should be displayed.

Note: These test cases are not exhaustive and additional test cases may need to be added based on the specific requirements of the product.

Test Plan:

Feature: Font settings Description: Ensure that the font settings are correctly implemented.

Test Cases:

1. Verify that the default font for the mobile phone is "calibri (Body)" with size 12.
2. Verify that changing the font in the settings to a different font applies the new font throughout the phone.
3. Verify that changing the font size in the settings to a different size applies the new size throughout the phone.
4. Verify that changing the font color in the settings to a different color applies the new color throughout the phone.

Test Steps:

1. Turn on the mobile phone and check that the default font is "calibri (Body)" with size 12.
2. Navigate to the font settings and change the font to a different font.
3. Navigate throughout the phone and ensure that the new font is applied to all text.
4. Navigate to the font settings and change the font size to a different size.
5. Navigate throughout the phone and ensure that the new font size is applied to all text.
6. Navigate to the font settings and change the font color to a different color.
7. Navigate throughout the phone and ensure that the new font color is applied to all text.

Test Plan for "Touch Responsiveness" Requirement:

Objective: To ensure that the user interface of the mobile phone is touch-responsive as per customer's requirement.

Test Approach: Black box testing

Test Environment: Actual device

Test Cases:

1. Verify that all touch gestures, such as tapping, swiping, pinching, and scrolling, are responsive and accurate.
2. Verify that the touch screen responds consistently across all areas of the display.
3. Verify that there are no noticeable delays or lags when interacting with the user interface via touch.
4. Verify that multi-touch gestures, such as two-finger pinch to zoom, are supported and function correctly.
5. Verify that the touch screen responds accurately to both light and heavy touches.
6. Verify that the touch screen responds accurately to touch when the device is charging.
7. Verify that the touch screen responds accurately to touch when the device is in low battery.
8. Verify that the touch screen responds accurately to touch when the device is in high-temperature environments.
9. Verify that the touch screen responds accurately to touch when the device is in low-temperature environments.
10. Verify that the touch screen works accurately when used with a screen protector or with gloves.

Test Deliverables:

1. Test cases document
2. Test logs
3. Defect report, if any.

Product: New Mobile Phone

Objective: To ensure that the mobile phone is functioning as per the requirements mentioned in the User Stories and is user-friendly.

Testing Type: Blackbox Testing

Testing Methodologies: Functional Testing, Usability Testing

Testing Techniques: Boundary Value Analysis, Equivalence Partitioning

Test Environment: Mobile testing lab with necessary hardware and software installed.

Test Plan:

1. Test Case ID: TP-US-01 Test Case Objective: To verify that the power button is long-pressed to switch on the phone with a company logo at the center of the screen. Test Procedure:

   • Press and hold the power button for a longer duration.
   • Observe if the phone is switched on with the company logo at the center of the screen.
   • Record the observations and the test result.

2. Test Case ID: TP-US-02 Test Case Objective: To verify that when the power button is pressed, the phone is switched on, and all the icons of the APPS are present in the grid. Test Procedure:

   • Press the power button to switch on the phone.
   • Check if all the icons of the APPS are present in the grid.
   • Record the observations and the test result.

3. Test Case ID: TP-US-03 Test Case Objective: To verify that the "Call the phone" icon is present as the first icon at the bottom bar of the screen when the phone is powered on. Test Procedure:

   • Power on the phone.
   • Check if the "Call the phone" icon is present as the first icon at the bottom bar of the screen.
   • Record the observations and the test result.

4. Test Case ID: TP-US-04 Test Case Objective: To verify that the "Dictionary" icon is present as the second icon at the bottom bar of the screen when the phone is powered on. Test Procedure:

   • Power on the phone.
   • Check if the "Dictionary" icon is present as the second icon at the bottom bar of the screen.
   • Record the observations and the test result.

5. Test Case ID: TP-US-05 Test Case Objective: To verify that all the contacts are visible based on chronological order when the "Call the phone" icon is clicked. Test Procedure:

   • Power on the phone.
   • Click the "Call the phone" icon.
   • Check if all the contacts are visible based on chronological order.
   • Record the observations and the test result.

6. Test Case ID: TP-US-06 Test Case Objective: To verify that a search bar appears at the middle of the screen to let the user search the meanings of the words desired when the "Dictionary" icon is clicked. Test Procedure:

   • Power on the phone.
   • Click the "Dictionary" icon.
   • Check if a search bar appears at the middle of the screen.
   • Record the observations and the test result.

7. Test Case ID: TP-US-07 Test Case Objective: To verify that the phone is switched off with the "Good-Bye" message when the power button is long-pressed. Test Procedure:

   • Press and hold the power button for a longer duration.
   • Check if the phone is switched off with the "Good-Bye" message.
   • Record the observations and the test result.

8. Test Case ID: TP-US-08 Test Case Objective: To verify that the font in the mobile is always "Calibri (Body)" and of size 12. Test Procedure:

   • Power on the phone.
   • Check if the font is "Calibri (Body)" and of