Project 1 - V&V SW Analysis - I

The detailed test plan for the testing is given below:

TABLE OF CONTENTS

1. Test Objective
2. Scope of Testing
3. In-scope features
4. Out-of-scope features
5. Roles and responsibilities
6. Schedule of tests
7. Assumptions
8. Risks
9. Mitigation/Contingency plans
10. Test Methodology
11. Test approach
12. Entry criteria
13. Exit criteria
14. Test environments
15. Defect tracking
16. Effort estimation
17. Test automation
18. Test deliverables

1. TEST OBJECTIVE:

The objective of the test is to determine the adherence of the features of a new mobile phone to the functional specifications and requirements that have been documented before production through black box testing.

2. SCOPE OF TESTING:

The scope of testing is to analyze the functional characteristics of the power button of the mobile phone, the display of the mobile phone, the functionality of the touch screen and the font size of the text that is displayed on the mobile phone. The details of the in-scope features of the phone is given in the next segment. The testing does not include unit testing of the specific details of the firmware of the phone. It does not include testing of battery life or other hardware tests. This test does not include the UA (User Acceptance Test)

3. IN-SCOPE FEATURES:
4. When the power button is long pressed when the phone is switched off , the phone shall switch ON with the company logo at the center of the screen
5. When the power button is switched on the phone is switched on and all the icons of the apps are visible in the grid on the screen
6. When the phone is powered on, the ‘call the phone icon’ should be seen as the first icon in the bottom bar of the screen
7. When the phone is powered on, the ‘dictionary’ icon should be seen as the second icon in the bottom bar of the screen
8. When ‘call the phone’ icon is clicked, all the contacts should be visible in chronological order
9. When the ‘dictionary’ icon is clicked, a search bar should appear at the center of the screen to search the meaning of the words that typed in
10. When the power on button is long pressed after the phone is powered on, the phone should switch off with a ‘Goodbye’ message at the center of the screen
11. The font in the mobile’s display should always be Calibri(body) and it should be of size 12
12. The user interface should be touch responsive
13. There should be no hard buttons on the mobile phone

4. OUT-OF-SCOPE FEATURES:
5. Functioning of all apps of the mobile phone except ‘call the phone’ and ‘dictionary’ icons
6. Testing of battery life
7. Testing of camera
8. Testing of mobile phone speakers
9. Testing of the port for connecting headphones
10. Testing of volume buttons
11. Testing of fingerprint scanner
12. Testing of the flashlight

5. ROLES AND RESPONSIBILITIES:
6. Quality Control Manager: Responsible for verifying that the test is conducted successfully on the scheduled date
7. Embedded tester 1: Responsible for executing the test plan and documenting the results
8. Embedded tester 2: Responsible for documenting the results of the test
9. Technicians: Available to assist the testers

6. SCHEDULE OF TESTS:

The tests are scheduled to be conducted on 13/09/2022 from 10:00 am to 12:00 pm

7. ASSUMPTIONS:
8. Embedded tester 1 and Embedded tester 2 will both be present in office for work on 13/09/2022 from 10:00 am to 12:00 pm
9. Development of the phone to include the features to be tested will be complete before the date of testing
10. The Quality Control manager will be able to dedicate the scheduled time for testing
11. The phone to be tested will not fall and get damaged during the testing

8. RISKS
9. Either Embedded tester 1 and Embedded tester 2 may not be available for work on the scheduled date or the Quality Control manager may not be able to dedicate his time for testing
10. The features to be tested may not be incorporated into the phone by the scheduled date
11. The phone may fall down and get damaged during the testing
12. A stakeholder may change the features needed in the phone before the testing date

9. MITIGATION/CONTINGENCY PLANS
10. If one embedded tester is unavailable for work on the scheduled date, then the testing can be carried out by the other embedded tester with an additional 2 hours for documenting the results i.e. from 10:00 am to 2:00 pm
11. Additional developers can be added to the development team to ensure that the features to be tested are incorporated into the mobile phone before the testing date
12. A spare mobile phone will be present at the testing site in case the mobile phone to be tested gets damaged during the testing
13. Stakeholders will be contacted 3 days before the testing date to confirm that they are happy with the features to be tested and don’t want any changes

10. TEST METHODOLOGY
11. The test will be a black box test of the features of the mobile phone mentioned in the in-scope features
12. The test employs error guessing technique to identify potential flaws in the product

11. TEST APPROACH

The prerequisites for the test are that the listed features should already be developed by the development team. The phone should display the listed features as per the in-scope features list. The test will be a black box test of the selected features which will be conducted manually by the two embedded testers under the supervision of the Quality Control manager.

12. ENTRY CRITERIA
13. The development of the phone should have progressed sufficiently to include the in-scope features in the mobile phone
14. Conductance of the test should be approved by the Quality Control manager
15. Clearance to use the test site should be obtained prior to the test

13. EXIT CRITERIA
14. The testing of all the listed features of the mobile phone should be completed and each feature should have either passed the test or appropriate corrective action should be clearly noted down
15. The test should be cleared by the Quality Control manager and the clearance certificate signed by him should be produced

14. TEST ENVIRONMENTS

The test site available for the testing will be booked for a time period of 2 hours from 10:00 am to 12:00 pm on 13/09/2022 with provision to extend it by 2 hours if necessary. Clearance for using the test site should be secured before 6:00 pm on 12/09/2022. Two computers will be made available to the embedded testers for documenting their results.

15. DEFECT TRACKING
16. JIRA serial numbers for power button – 111, call the phone icon – 112, dictionary icon – 113, font size – 114, company logo – 115, goodbye message – 116

16. EFFORT ESTIMATION

The testing requires two hours of effort from two embedded testers to test the listed features and document the result. It requires the Quality Control manager to dedicate two hours to supervise over the testing and ensure that the test is executed as per the test plan.

17. TEST AUTOMATION

The testing cannot be automated since it is black box testing and the possible flaws are uncovered by error guessing which requires experienced engineers with expertise. The features to be tested such as long press of power button and short press of power button have to be done manually.

18. TEST DELIVERABLES
19. The test report with the outcome of each test whether it has passed or failed
20. Test clearance certificate signed by the Quality Control manager giving permission to move on to the next stage of development

I will attach the word document of the test plan for reference.

===============================END==================================