Task5:Test Case and bug Reporting

Q1:https://docs.google.com/spreadsheets/d/19RvwiWE9pdvLwzEXPP91zTwzT1JcRFN_pgYGls3nLCw/edit#gid=109964555

Q2:Test Scenario:

Definition:

A test scenario is a description of a specific functionality or feature to be tested.

Generally test scenario is written one line. It represents a specific condition or situation that needs to be verified during testing.

Characteristics:

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.

Purpose:

Test scenarios help identify high-level requirements and functionalities to be tested.They assist in understanding the overall flow of the system or application.

Test Case:

Definition:

A test case is a set of conditions or variables under which a software tester will determine whether a system or application is working correctly or not.

Components:

Test cases consist of preconditions, input data, expected results, actual results and steps to execute the test.They are designed to cover specific functionalities in a detailed manner.

Purpose:

Test cases provide detailed instructions for testers to execute.They help in ensuring that the software behaves as intended under various conditions.

Test Strategy:

Definition:

A test strategy is a high-level document that defines the overall testing approach for a project.

Components:

It includes 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.

Purpose:

Test strategy provides a roadmap for how testing will be conducted. It ensures that testing efforts align with project goals and objectives.

Test Plan:

Definition:

A test plan is a comprehensive document that outlines the testing approach, scope, resources, schedule, and deliverables for a testing project.

Components:

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.

Purpose:

Test plan serves as a guide for the entire testing process. It ensures that testing is organized, systematic, and aligned with project requirements.

Test Summary Report:

Definition:

A test summary report is a document that provides an overview of the testing activities, results, and overall quality of the software after testing is completed.

Components:

It includes a summary of executed test cases, defects found, test coverage, and an assessment of whether testing goals were met. The report may also include recommendations for further improvements.

Purpose:

Test summary report 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.