📓Test Cases

What is a Test Case?

A test case serves as a predefined set of conditions or activities designed to validate the functionality of a software program or system. It encompasses a comprehensive description of the inputs, preconditions, steps to be executed, and expected outcomes. Test cases are meticulously written to target specific aspects or functionalities of the software, ensuring that they align with the established requirements and meet the desired objectives.

The primary purpose of running test cases is to identify any defects or issues in the application so that they can be fixed before the application is released to itend users.

Here are some key points that will give you a good understanding of test cases:

• Manual and Automated Test Case Creation: You can create testing cases manually or by automated approach.

• Manual Test Case Creation and Execution: The tester creates manual testing cases and follows the steps outlined to verify the application’s functionality.

• Automated Test Case Execution with Test Tools: Using test tools and frameworks, automated testing cases are executed, which follow Software Requirement Specification (SRS).

• Structured Approach to Functionality Verification: It provides a structured approach to verify the functionality of software applications.

• Independence of Test Cases: They are not dependent on each other, meaning that the result of one test case should not impact the result of another.

• Controlled Execution Environment for Test Cases: You can execute the test case in a controlled environment, ensuring the availability of all necessary resources without impacting the software production environment.

What are Manual Test Cases? 📋

Manual test cases are step-by-step test execution instructions that are performed manually by a human tester without using any automated tools or scripts.

Why Create Manual Test Cases? 🤔

Manual test cases are created to:

• Validate that the system meets the requirements and user expectations. ✅

• Provide a repeatable and consistent testing approach. 🔁

• Reduce ambiguity for testers on what to test.🎯

• Serve as documentation of what was tested. 📄

• Help estimate testing effort. 🕑

What's Included in a Test Case? 🗒️

Key elements of a manual test case:

• Test Case ID:verifying Unique identifier

• Test Scenario - What is being tested 🧪

• Prerequisites - Preconditions required 🔍

• Test Steps - Detailed test execution steps 👣

• Expected Result - Predicted result for test to pass ✅

• Actual Result - Observed result during test execution 👀

• Status - Pass, Fail, Blocked ❌

How To Write Good Test Cases 📝

Good test cases are:

• Well structured and detailed 🪜

• Atomic - Test one thing at a time 🍳

• Have clear expected results ✅

• Easy to follow and execute 🧭

• Traceable to requirements 📌

Tips for Effective Manual Testing 💡

• Use test case management tools ♾️

• Leverage test case reviews and version control 👥

• Group related test cases into test suites 🗂️

• Prioritize test cases based on risk ⚠️

• Automate repeatable test cases 🤖

Key Takeaways 📝

• Manual test cases are essential for consistent, high-quality testing 🔎

• Well-written test cases improve efficiency and defect detection 🕵️

• Traceable, atomic, and detailed test cases provide the most value 💯

Test Scenario Vs Test Case

Test scenarios are rather vague and cover a wide range of possibilities. Testing is all about being very specific.

Test Scenario: Check Login Functionality

• Test Case 1: Check results on entering valid User Id & Password

• Test Case 2: Check results on entering Invalid User ID & Password

• Test Case 3: Check response when a User ID is Empty & Login Button is pressed