[PART 3] Pengenalan & Cara membuat Test Cases | SQA Journey Path

Summary

The video provides a detailed guide on creating and executing test cases for software applications, using a demo website as an example. It explains the components of a test case, including action steps, expected results, actual results, and status, while emphasizing the importance of sequential steps for easier execution and reporting. The presenter demonstrates both valid and invalid login scenarios, highlighting how to document outcomes and handle errors. The tutorial also covers using project management tools like Jira or TestRail for organizing test cases and offers practical tips for practicing with dummy data to prepare for real-world testing projects.

Takeaways

• 😀 A test case is a series of steps designed to verify specific functionality or features of software or an application.
• 😀 Key components of a test case include action steps, test data, prerequisites, post-conditions, and expected results.
• 😀 Test case templates may vary across companies, but the main structure and purpose remain consistent.
• 😀 Project management and testing tools like Jira and TestRail are commonly used to organize and execute test cases.
• 😀 Each test case should have a unique identifier (TC-ID) for easy tracking and reference.
• 😀 Test cases can include both positive scenarios (e.g., valid login) and negative scenarios (e.g., login without credentials).
• 😀 Expected results are defined based on the scenario, and actual results are compared to determine the test status (Pass or Fail).
• 😀 Organizing test steps in sequence improves clarity, execution efficiency, and reporting.
• 😀 Practical execution of test cases on demo websites helps users practice and understand the testing process.
• 😀 Templates should be structured for easy reporting and can be adapted for both manual and automated testing.
• 😀 Error handling and edge cases (like failed logins) should be explicitly captured in the test case to ensure comprehensive testing.

Q & A

What is a test case in software testing?

A test case is a sequence of actions carried out to verify specific features or functionality of an application or software. It includes steps, prerequisites, expected outcomes, and post-conditions.

What are the key components of a test case as described in the video?

The key components include the Story (feature being tested), TC-ID (unique identifier), Source (test condition), Action Steps, Expected Result, Actual Result, and Status.

What is the purpose of the TC-ID in a test case?

The TC-ID is a unique identifier used to distinguish and reference each test case. For example, 'LG001' might represent the first login test case.

How should action steps be structured in a test case?

Action steps should be clear and sequential, showing exactly what actions need to be taken during the test, such as opening a website, entering credentials, and clicking the login button.

What is an expected result in a test case?

The expected result describes what should happen if the test case passes. For example, a successful login should redirect the user to the homepage and display products.

What should be done if the actual result does not match the expected result?

If the actual result does not match the expected result, the status of the test case is marked as 'Fail,' and the error or discrepancy should be recorded for review.

Can you give an example of a test case for login functionality?

Yes. Scenario: Valid Login. Steps: open demo website, enter username and password, click login. Expected result: user successfully logs in and navigates to the homepage.

What happens if login credentials are left blank in the test case?

If login credentials are left blank and the login button is clicked, the expected result is that an error message appears indicating the login failed.

Why is it helpful to use a test case template?

A test case template ensures consistency, helps organize steps, makes execution easier, and simplifies reporting of results across multiple test cases or users.

Which tools were mentioned that can be used to manage test cases?

The video mentions tools like Jira and TestRail, which are part of project management systems commonly used in companies for organizing and tracking test cases.

What is the significance of using a demo website for practice?

Using a demo website, like sausdemo.com, allows users to practice creating and executing test cases safely without affecting real systems or data.

How should test steps and expected results be ordered for better execution?

Test steps and expected results should be arranged in a logical sequence that matches the workflow, making it easier to execute the test and report results accurately.