Project 1 - V&V SW Analysis - I

Test Plan to test features of a new mobile phone:

Overview:

A Test Plan is a document that describes the scope of testing, test strategy, objective, effort, schedule, and resources required. It serves as a guide to testing throughout the development process.

2.1 Unit testing

Objective

The main objective of unit testing is to verify whether every unit operates as intended. A function, procedure, method, or even the entire module can be considered a separate unit. Unit testing can be conducted manually, but automated testing is a more common practice.

Entry criteria

• The planning phase has been finished
• Testable units are available
• all functional requirements have been defined
• the unit testing environment has been set up.

Exit Criteria

• All planned test cases have been covered
• all the bugs found have been reviewed
• the performance of the key modules has been tested

Logging Tests and Reporting

Developers fix the defects found in each unit. If these defects are related to other modules and units, they must be reported.

System Testing

objective

System testing is generally conducted after unit testing. The objective of the System Testing is to evaluate the compliance of an integrated application with its requirement

Testing Procedure:

Test cases preparation

• test execution
• bug reporting

Types of System Testing

Performance Testing

Performing testing is conducted to detect issues related to:

• memory consumption
• power utilization
• network connectivity
• operating in the background
• switch between application
• memory leakage

Interrupt Testing

This testing type examines how an application reacts to interruption and resumes its previous state. Numerous reasons can potentially interrupt the operations of an app, such as getting a phone call, message, etc.

Usability Testing

Usability testing is performed to check whether the application is easy to use and understand for the end-user.

Functional Testing

• All the functions and features of the application are tested to verify whether they operate according to the specification.
• Security Testing
• Regression Testing

Test Report:

• Name and overview of an application
• Testing the hardware and software environment
• The number of tests executed
• bug description
• bug status
• bug location

3. Risks and Assumptions

Risks

The following risks may occur during the mobile app testing process:

• availability of devices
• new features and modifications which have not been planned in advance
• changes in requirements
• delays in schedule

Assumption

• Each release is accompanied by a note with the information about implemented feature and the impact on the system
• All blocker bugs receive the high priority status
• All the bugs found are fixed before the next software release
• all documents are up to date and delivered to the testing tea in time

4. Entry and Exit Criteria

Entry Criteria

• the development phase has been finished
• requirements have been defined and approved
• test design and tests plan have been created

Exit criteria

• Test cases are executed
• The rate of test cases passed is satisfactory, eg 95%
• Test results have been accepted

Test Meteric:

• Requirement coverage
• test cases coverage
• number of test executed
• test design effort
• total test effort

Code:

if(owner switch on the phone)

{

((company logoat the center of the screen))

}

else if(customer switch on the phone)

{

(all my icons of the APPs shall be present in the grid)

}

else if(owner powered on the phone)

{

(the "call the phone" icon is the first icon and the "Dictionary" icon is the second icon at the bottom bar of my screen.)

}

else if (owner clicked on the phone icon)

{

(all the contact shall be visible based on chronological order)

}

else if(owner clicked on phone icon)

{

(All the contacts shall be visible based on chronological order.)

}

else if(owner access the dictionary icon)

{

(search bar shall appear in the middle of the screen to let me search for the meaning of the words I desire)

}

else if(owner switches off the phone)

{

("Goodbye" message should appear with font caliber and font size shall be 12)

}

else if(customer)

{

(i need my UI must be touch responsible)

}

else

{

(mobile phones should not have hard buttons

}