thank you sir ..helping this video for me

Good work

Thank you sir.. If possible make a video using any test management tool or if you already made the video please share the link..

Too good 🙏🏽

Excellent tutorial Manash..👍🙏

thanks for guidance

Thank you.

make more example for getting confidence to us.....very nicely taught

Thank you sir

Good Teaching.its video is helpful .thanks

@softwaretestingmentor

2 жыл бұрын

You are most welcome. Keep watching for more videos.

THANK YOUUUUUUU

Thank you so much!

@softwaretestingmentor

10 ай бұрын

You're most welcome. 😊 Keep watching for more videos and tutorials.

Thank you so much for this video so informative ! can you please upload more videos using real project like this so I can have more ideas to enhance more confidence especially for test case for checking purchase

@softwaretestingmentor

3 жыл бұрын

Sure coming soon! Thanks

Great performance and For beginners it’s very clear.

@softwaretestingmentor

3 ай бұрын

Thanks a lot! Keep watching and sharing.

Thank you so much

@softwaretestingmentor

Жыл бұрын

You're most welcome

**Notes: How to Write Test Cases - Software Testing Tutorial #32** **Understanding Test Cases:** - Test cases are documents describing the step-by-step process for testing software. - They ensure that software meets user requirements. **Essential Fields in a Test Case Template:** 1. **Test Case ID:** Unique identifier for the test case. 2. **Created By:** The name of the person creating the test case. 3. **Reviewed By:** The person responsible for reviewing the test case. 4. **Priority:** The test case's priority (e.g., high, medium, low). 5. **Prerequisites:** Conditions required before executing the test case. 6. **Title:** A brief description of what the test case covers. 7. **Description:** Detailed information about the test case. 8. **Steps:** Sequential instructions for executing the test. - **Step Number:** The order of each step. - **Test Step:** The operation to be executed. 9. **Test Data:** Any data required for a test step. 10. **Expected Result:** The anticipated outcome of the test step. 11. **Actual Result:** The observed outcome when the test step is executed. 12. **Execution Details:** Information about test execution, including pass, fail, or other statuses. 13. **Comments:** Additional notes or comments about the test case. **Example Test Case - Verifying an E-commerce Website:** - **Test Case ID:** tc_0001 (or auto-generated in a test management tool) - **Created By:** Your name - **Reviewed By:** [Leave blank until reviewed] - **Priority:** High - **Prerequisites:** Edge browser installed - **Title:** Verify that electronics category filters only electronic items. - **Description:** Check if the electronics category displays only electronic items and doesn't mix products from other categories. - **Steps:** - **Step 1:** Launch the website URL in Edge browser. - **Test Data:** [Amazon URL] - **Expected Result:** The website should launch successfully. - **Step 2:** Click on the electronics category. - **Test Data:** [N/A] - **Expected Result:** The electronics category page should get displayed successfully. - **Step 3:** Scroll to the bottom of the page and verify the products on the page. - **Test Data:** [N/A] - **Expected Result:** Only electronics items should be filtered and displayed. - **Test Data:** [Leave blank unless needed] - **Expected Result:** [Leave blank unless needed] - **Actual Result:** [Fill this during test execution] - **Execution Details:** - **Executed By:** Your name - **Execution Date:** [Date of execution] - **Tasks:** Pass/Fail/Blocked, etc. - **Comments:** [Any comments related to test execution]

I want do we need to mentione test scenario name or i think here description is the test scenario know

Only one thing 🙏

sir im learning from you can u make excel videos pls

Question. A single test case would be executed multiple times with different builds, browsers. so how is that captured and where is it stored in practical scenarios?

@suganthym1438

Жыл бұрын

Answered @17 minutes. My understanding.. So create a copy execute for release update doc and place in designated folder ( version controlled?)