Test management tools (Jira, TestRail) in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new test case in TestRail using the API.

Testing Fundamentals

response = client.[1]('add_case/1', data)

Drag options to blanks, or click blank then click option'

Anew_case

Bcreate_case

Cadd_case

Dpost_case

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'create_case' instead of 'add_case' causes an API error.

Using 'post_case' is not a valid method in TestRail API.

In TestRail API, the method to add a new test case is add_case.

2fill in blank

medium

Complete the code to filter Jira issues by status using JQL.

Testing Fundamentals

jql_query = 'project = TEST AND status = [1]'

Drag options to blanks, or click blank then click option'

A'In Progress'

B'Resolved'

C'Closed'

D'Open'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Closed' will filter only finished issues, not active ones.

Using 'Open' might include issues not yet started.

The JQL status 'In Progress' filters issues currently being worked on.

3fill in blank

hard

Fix the error in the code to update a test run status in TestRail.

Testing Fundamentals

client.[1](run_id, {'status_id': 1})

Drag options to blanks, or click blank then click option'

Aupdate_run_result

Bset_run_status

Cupdate_run_status

Dupdate_run

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'update_run' only updates run details, not results.

Using 'set_run_status' is not a valid API method.

The correct TestRail API method to update a test run result status is update_run_result.

4fill in blank

hard

Fill both blanks to create a Jira issue with a summary and description.

Testing Fundamentals

issue_dict = {'fields': {'summary': [1], 'description': [2], 'project': {'key': 'TEST'}, 'issuetype': {'name': 'Bug'}}}

Drag options to blanks, or click blank then click option'

A'Test failure in login'

B'Login button does not respond'

C'Bug in login module'

D'Steps to reproduce the issue'

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping summary and description values.

Using too long text for summary.

The summary is a short title like 'Test failure in login', and the description explains details like 'Steps to reproduce the issue'.

5fill in blank

hard

Fill all three blanks to create a TestRail test run with a name, description, and suite ID.

Testing Fundamentals

run_data = {'name': [1], 'description': [2], 'suite_id': [3]

Drag options to blanks, or click blank then click option'

A'Regression Test Run'

B'Run for release 1.2'

C5

D10

Attempts:

3 left

💡 Hint

Common Mistakes

Using numbers as strings for suite_id.

Mixing up name and description values.

The name is 'Regression Test Run', the description explains 'Run for release 1.2', and the suite_id is the numeric ID 5.

Practice

1. What is the primary purpose of test management tools like Jira and TestRail?

easy

A. To design user interfaces

B. To write code for software applications

C. To manage server hardware

D. To organize and track testing activities and results

Solution

1. Step 1: Understand the role of test management tools

   Test management tools help testers organize test cases, track progress, and report bugs.

2. Step 2: Compare options with this role

   Only To organize and track testing activities and results describes organizing and tracking testing activities, which matches the tool's purpose.

3. Final Answer:

   To organize and track testing activities and results -> Option D

4. Quick Check:

   Test management tools = Organize and track tests [OK]

Hint: Think: What helps testers track and organize tests? [OK]

Common Mistakes:

• Confusing test management with coding or design tools
• Thinking test management tools handle hardware
• Assuming they write software code

2. Which of the following is a correct way to create a new test case in TestRail?

easy

A. Send test case via email to TestRail support

B. Write test case in a text editor and upload as .exe

C. Click 'Add Test Case', fill details, then save

D. Create a new project in Jira instead

Solution

1. Step 1: Recall TestRail test case creation process

   TestRail allows adding test cases by clicking 'Add Test Case', entering details, and saving.

2. Step 2: Evaluate other options

   Uploading .exe files or emailing support are not standard ways; creating a Jira project is unrelated.

3. Final Answer:

   Click 'Add Test Case', fill details, then save -> Option C

4. Quick Check:

   TestRail test case creation = Add and save [OK]

Hint: TestRail uses UI buttons to add test cases, not files or emails [OK]

Common Mistakes:

• Confusing file upload with test case creation
• Mixing Jira project creation with TestRail test cases
• Thinking support emails create test cases

3. In Jira, if you create a bug issue and assign it to a developer, what will happen when the developer changes the status to 'In Progress'?

medium

A. The bug is marked as fixed automatically

B. The bug status updates to show work has started

C. The bug is deleted from the project

D. The bug is reassigned to the tester

Solution

1. Step 1: Understand Jira issue workflow

   Changing status to 'In Progress' means work on the bug has started, not fixed or deleted.

2. Step 2: Match options with workflow behavior

   Only The bug status updates to show work has started correctly describes status update showing work started.

3. Final Answer:

   The bug status updates to show work has started -> Option B

4. Quick Check:

   Jira 'In Progress' = Work started [OK]

Hint: In Jira, 'In Progress' means work started, not fixed or deleted [OK]

Common Mistakes:

• Thinking 'In Progress' means bug is fixed
• Assuming bug gets deleted automatically
• Confusing status change with reassignment

4. You notice that test cases in TestRail are not linked to Jira issues as expected. What is the most likely cause?

medium

A. The integration between TestRail and Jira is not configured properly

B. TestRail does not support linking to Jira

C. Jira issues are deleted automatically after creation

D. Test cases must be manually copied into Jira

Solution

1. Step 1: Understand integration role

   TestRail can link test cases to Jira issues if integration is set up correctly.

2. Step 2: Analyze options

   The integration between TestRail and Jira is not configured properly explains missing links due to misconfiguration; others are incorrect or false statements.

3. Final Answer:

   The integration between TestRail and Jira is not configured properly -> Option A

4. Quick Check:

   Missing links = Integration issue [OK]

Hint: Check integration settings first when links are missing [OK]

Common Mistakes:

• Assuming TestRail cannot link to Jira
• Thinking Jira deletes issues automatically
• Believing manual copying is required

5. A team uses Jira for bug tracking and TestRail for test case management. They want to generate a report showing which test cases failed due to open bugs. What is the best approach?

hard

A. Use TestRail-Jira integration to link test cases with Jira bugs, then generate combined reports

B. Manually compare test case results and Jira bugs in separate spreadsheets

C. Export Jira bugs and import them into TestRail as test cases

D. Create duplicate test cases in Jira and track failures there

Solution

1. Step 1: Identify integration benefits

   Linking test cases and bugs via integration allows automatic combined reporting.

2. Step 2: Evaluate other options

   Manual comparison is error-prone; importing bugs as test cases or duplicating test cases in Jira is inefficient and incorrect.

3. Final Answer:

   Use TestRail-Jira integration to link test cases with Jira bugs, then generate combined reports -> Option A

4. Quick Check:

   Integration enables combined reporting [OK]

Hint: Leverage integration for combined reports, avoid manual work [OK]

Common Mistakes:

• Relying on manual spreadsheet comparison
• Importing bugs as test cases incorrectly
• Duplicating test cases in Jira unnecessarily