TASK - 5
Published: 2024-04-29 06:56:07

**Scenario based questions:
Q-1-> Write as many test cases as you can for a given scenario using excel sheet. The excel sheet should include the following columns:** 

**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,TC-3..TCn.
Test steps: A detailed list of the steps to be followed to execute the test case.
Input: The input of each step taken by user.
Expected results: The expected outcome of each step in the test case.
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.**

<u>**Answer**</u>
https://docs.google.com/document/d/1rvxkVbUonndIqZy-UzfKjJd2CpaeLpdh9b2cNbo2rag/edit?usp=sharing

===============================================

**Q-2-> Write the key points on test scenario, test case, test strategy and plan, test summary report.**

<u>**Answer**</u>
**Test Scenario**
Test scenario is a documentation of test cases. It also called as test condition or test possibility. It is a description of any specific functionality or feature to be tested. Every scenario has unique id to track during testing. Mostly, Test scenario is written in one or two lines and approved by business analyst or team manager or lead.
Ex : TS_4 {verify the login functionality is working perfectly}

**Test Case**
Test case is set of actions or steps to perform the testing of any specific functionality. Every test case has unique id like scenario and mapped with their respective scenario. It contains expected result, actual result, steps, inputs and pass/fail. Test cases are more important than others in testing phase and it should be maintained by companies.
Example : TC_3 {verify the login with valid username and invalid password}

**Test Strategy**
The test strategy is a high-level document used to validate the test levels to be executed for the product. And it also describes what kind of technique has to be used and which module will be tested.The Test Strategy's main purpose is to deliver a systematic approach to the software testing process to ensure reliability, quality, traceability, and better planning.

- It is derived with the help of Use Case documents, SRS (Software Requirement Specification), and Product Description.
- A test plan is developed by Test Lead or test/ Project manager.
- A test plan defines the whole testing activities thoroughly.
- A test plan is a dynamic document that can be updated frequently when new requirements or modifications have occurred.

**Test Plan**
The test plan is a base of software testing. It is a detailed document, which includes several testing attributes such as test objectives, scope, test schedule, template, required resources (human resources, software, and hardware), test estimation and test deliverables, risk, mitigation plan, defect tracking, entry and exit criteria, test environment, etc.

- While the Test Strategy can be derived with the help of the BRS (Business Requirement Specification) document.
- Generally, the test strategy is developed by the Business Analyst and approved by the Project Manager.
- It is a static document, which implies that it cannot be changed or modified.
- The test strategy defines high-level test design methods.