1.3. Sample Test Case in JIRA

Field Example Test Summary Verify login with valid credentials Precondition User is registered

In this chunk, we define the primary fields that outline a sample test case in JIRA. Each test case will have several components:

• Field: This is a label or name for each section of the test case.
• Example: This is the actual data or template used in that field. For example, under 'Test Summary', we write 'Verify login with valid credentials', which clearly states the purpose of the test case.
• Precondition: This indicates any conditions that must be met before the test case can be executed. Here, 'User is registered' signifies that the user must be an existing member of the system to test the login functionality.

Think of the test case as a recipe in cooking. Just like a recipe has necessary ingredients and steps to create a dish, a test case contains fields (ingredients) like summary and preconditions, which are needed to successfully conduct the test (make the dish).

Test Steps

1. Enter username
2. Enter password
3. Click login

This chunk outlines the specific steps required to perform the test. Each step should be clear and concise to ensure that anyone carrying out the test will understand what to do:

1. Enter username: This directs the tester to type in the username.
2. Enter password: This directs the tester to input the password associated with the username.
3. Click login: This instructs the tester to submit the entered credentials by clicking the login button.

Imagine following a step-by-step guide to build a piece of furniture. Each step tells you what action to take, much like these test steps guide you through the process of logging into an application.

Expected Result User lands on dashboard

In this chunk, we discuss the expected outcome of executing the test case. The 'Expected Result' defines what the tester should see after completing all the test steps. In this case, the expected outcome is that the 'User lands on dashboard'. This sets a clear expectation for the test's success or failure based on whether this result is achieved.

When taking a test for your driver’s license, the expected result is to pass and receive your license. Similarly, in testing, we expect to verify that a user reaches the dashboard, confirming that the login process works correctly.

🛠 Add-ons like Zephyr or Xray are required to manage test cases natively in JIRA.

This chunk highlights that in order to manage test cases directly within JIRA, additional tools or add-ons such as Zephyr or Xray are necessary. These tools extend JIRA's capabilities to not only track bugs and issues but also to formulate and manage test cases more effectively within the platform.

Consider JIRA as a standard toolbox; it's useful for many tasks, but sometimes you need specialized tools—like a drill or a saw—to complete specific projects. In this analogy, Zephyr or Xray are the specialized tools that enhance JIRA's basic functionalities.

--