Project 1 - V&V SW Analysis - I

What is a Test Plan?

• It is detailed documentation that provides information about all the necessary resources and activities that will be a part of SW/HW testing.
• Test plans are necessary documentation used in both black box and white box testing.
• It has various attributes detailing the Test Objective, Scope of Testing, Roles and Responsibilities, Schedule of Tests, Assumptions, Risks, Mitigation/Contingency Plans, In-scope Features, Out-of-scope Features, Test Methodology, Test Approach, Entry Criteria, Exit Criteria, Defect Tracking, Test Environments, Test Automation, Effort Estimation, and Test Deliverables.

Components of Test Plan

All components of the test plan are mandatory.

• Test Objective:Illustrate the objective of the test, that is, what are we going to test (Features - Functional/Non-functional).
• Scope of Testing: Illustrate the scope of the test.
• In-scope Features: Features that fall under the scope to be tested
• Out-of-scope Features: Features that do not fall under the scope to be tested

• Roles and Responsibilities: Lists the Roles and Responsibilities of the test team.

• Schedule of Tests: When will the tests gets completed (on what date) with respect to the milestones planned?

• Assumptions: Assumptions of the test and Highly important

• Risks: Risks related to the availability of resources, availability of test environments (test setups), technical knowledge of the team, etc.

• Mitigation/Contingency Plans: Contingency plans related to stabilizing and addressing risks in a structured fashion.

• Test Methodology: Methodology we implement (CFT, ECT, STT, EG, etc.)

• Test Approach: Specifying the test approach to implement testing using test methodology (Analyze the prerequisites, Clarify SW acceptance criteria, outline the test approach to the QA Management team, define and identify the approach to test execution).

  o It defines how we will approach the test implementation for any requirement.

• Entry Criteria: The criteria that shall be met before we start executing a test case.

  o Predefined set of conditions that shall be met.

• Exit Criteria: The criteria that shall be fulfilled to complete the SW testing life cycle (STLC).

• Test Environments: Environment required to start and complete the testing activities without hindrance.

• Defect Tracking:

  o Illustrate the tracking of bugs reported during various phases of SW testing (E.g., using JIRA).

  o Normally, a link to JIRA shall be provided.

• Effort Estimation: Illustrate a detailed estimation of the effort required by the test engineers in the team to carry out the testing activity.

• Test Automation: Illustrate the required automation for the features that are tested manually, the scripting language used, link to the scripts, etc.

• Test Deliverables: Illustrate a detailed list of all the test deliverables that will be an output of the testing activity.

Methods of Testing:-

Black-box Testing:-

A method of testing that tests the functionality of the system without looking into the internal implementation/structures of the system.

E.g., Testing the lock and unlock features of your mobile.

White-box Testing:-

o A method of testing that may/may not test the functionality of the system by looking deep into the internal implementation/structures (design, coding, etc.) of the system.

o E.g., Testing any embedded prototype you designed by debugging into the software.

Unit Testing :- is an example of white-box testing without actually concerning about the functionality of code.

Regression Testing:-

A method of testing that tests all the functional and non-functional codes of an embedded software after we perform a change/modify any requirement.

SOLUTION:-