Q2.
Key points on :
Test Scenario:
A test scenario is a description of a specific test case that includes inputs, actions, and
expected outcomes. For example, a test scenario for a login system might involve entering
valid credentials and expecting successful login, or entering invalid credentials and expecting
an error message.
Test case:
A test case is a detailed set of instructions or conditions that describe a specific scenario to be
tested. For example, a test case for an e-commerce website checkout process might include
steps like adding items to the cart, entering shipping information, selecting a payment
method, and verifying the order confirmation page.
Test strategy:
A test strategy is an overarching plan that outlines the approach, objectives, resources, and
methods for testing a software product or system. For example, a test strategy for a mobile
app might include testing on various devices, using automation tools for regression testing,
and prioritizing testing based on critical functionalities.
Test plan:
A test plan is a document that outlines the scope, objectives, resources, schedule, and
approach for testing a specific software product or system. For example, a test plan for a web
application might include test objectives like validating user authentication, testing navigation
across different pages, and checking form submissions. It would also specify the testing tools,
environments, and responsibilities of team members involved in the testing process.
Test summary report:
A test summary report is a document that provides an overview of the testing activities,
results, and findings from a specific testing phase or project. For example, a test summary
report for a software release might include details such as the number of test cases executed,
defects found, test coverage achieved, and a summary of the overall testing effort. It provides
stakeholders with a snapshot of the testing status and helps in decision-making for further
actions or improvements.