Q1) Write the key points on Test Scenario, Test Case, Test Strategy and Plan, Test Summary Report.

Test Scenario:

Definition: A test scenario is a documentation of test cases. It is a description of a specific functionality or feature to be tested. Generally test scenario is written in one line. It represents a specific condition or situation that needs to be verified during testing.

Composed of:

Test scenarios are typically broad in concept and cover multiple test cases related to a specific feature. They are user-centric and describe real-life situations or interactions with the software.

Goal:

To ensure that all the features offered by the app are working properly. It is important to get input from customers, stakeholders, and developers in order to create accurate test scenarios.

Test Case:

Definition:

It is a series of steps, or a set of execution conditions, with specified inputs to test the correct behavior/functionality, and features of the application. A test case is a feature or function that should be run with a set number of inputs and given certain conditions and produce results that match what you expected.

Contains:

Input data, expected results, actual results and steps to execute the test.

Goal: The goal of a test case is to divide software functionality into a small unit of function that can be tested with specified input and generate a measurable result.

Test Strategy:

Definition:

A test strategy is a high-level document that defines the overall testing approach for a project. Once the test plan has been written and approved by the project manager and development team, it cannot be changed.

Contains:

Testing objectives, testing scope, testing phases, resource allocation, and entry/exit criteria. Test strategy may also define the test levels, test types, and the testing environment.

Goal:

To ensure that all purposes are fully addressed and understood by all stakeholders, we should systematically design a test strategy. This is the main goal of writing the test strategy.

Test Plan:

Definition:

A test plan is a document that outlines the testing methodology for a given system. It is the basis for testing software or machines. The test plan provides detailed information regarding the test project and the resources to be utilized during testing.

Contains:

Test plan includes test objectives, test scope, test schedule, resource requirements, test environment, and exit criteria. It may also contain test deliverables, testing tasks, and responsibilities.

Goal:

Test plan explains the methodology used by the testing team to evaluate the product as well as the outcomes.

Test Summary Report:

Definition:

It is also known as a Test Closure Report. It comprehensively summarizes the testing activities and results, including any issues and bugs found and resolved during the testing phase.

Contains:

It includes a summary of executed test cases, test scope, testing environment, testing methodologies, test cases, and any issues and defects identified and resolved during testing.

Goal:

Test summary report summarises the overall results of the entire testing process. It communicates the testing outcomes to stakeholders. It provides insights into the quality of the software and helps in decision-making for the release of the product.

These are the key features on Test Scenario, Test Case, Test Strategy and Plan, Test Summary Report.

Q2. Write as many test cases as you can for a given scenario in the Excel sheet.

Website Link:

https://in.bookmyshow.com

* Test Scenario ID(Requirement Matrix/User Story): A unique identifier for each test case.For Ex:TS-1,TS-2,TS-3...TSn.Test Scenario: A brief description of the test case.

*Test Case ID: A unique ID for testcase Forex: TC-1,TC-2....TCn

*Test Steps: A detailed list of the steps to be followed to execute the test case.

*Expected Results: The expected outcome of each step in the test case.

*Input: The input of each step taken by user.

*Actual Results: The actual outcome of each step in the test case.

*Pass/Fail: Whether the test case passed or failed.

*Test Case Complexity

*Test Case Severity.

Below is the table that contains Module, Test Scenario ID , Scenario name and Scenario Description:

Below is the Test case description, Test cases, Expected Results, Actual Results, Pass/Fail, Test case complexity and Test case severity:

Thus the Table with the required Test Scenarios , Test Cases with Test Steps, Expected and Actual outputs are all written.