Software Bug Reporting Guide

What information is NOT required when reporting a bug?

Which severity type indicates the highest priority for fixing a bug?

Where can you find the option to modify the bug reporting form in Jira?

Which field should contain a freeform description of the bug?

What must be included in the Summary field when reporting a bug?

In which type of report should the actual outcome of the test be detailed?

What type of field is the 'Severity' in the bug reporting form?

What is the purpose of the 'To Reproduce' section in a bug report?

What is the purpose of assigning labels to bug reports?

What type of information can be attached to a bug report?

Which type of link should be used to associate a bug report with its original test issue?

What distinguishes a critical bug from a high priority bug?

What is the primary use of the severity categorization in bug reporting?

Why are low priority bugs often shipped with software products?

How does the process of assigning bugs work in Jira?

What is a cosmetic bug?

Software Bug Reporting

Purpose: To document and report software bugs found during testing.
Essential Information:
- Test identifier (ID) that failed
- Environment where the bug occurred
- Steps to reproduce the bug
- Actual result of the test
- Severity of the bug
Bug Reporting Form Fields:
- Summary: Brief one-line description, including the test ID.
- Description: Detailed freeform description of the bug.
- Test ID: Identifier of the failed test; or description of how the bug was found if not test-related.
- Platform: Hardware platform (e.g., Windows PC, Mac, AWS).
- Operating System: OS used.
- Browser (if applicable): Type and version of web browser used.
- Expected Result: Expected outcome of the test.
- Actual Result: Observed result of the test.
- Steps to Reproduce: Precise steps to recreate the issue.
- Labels: Categorization tags, e.g., test-failure, UI-bug, performance-bug (allows filtering).
- Attachments: Supporting files like screenshots, logs, test data.
- Linked Issue: Link to the original test case using "related to" and a test identifier search.
- Severity:
  - Critical: Show-stopper, system unusability.
  - High: Impacts functionality, should be fixed soon.
  - Medium: Less critical than high, still needs fixing.
  - Low: Can wait until higher-priority bugs are fixed.
  - Cosmetic: Affects appearance but not functionality.

Jira Integration

Modification: Bug reporting form can be customized in Jira's project settings.
Customization: Fields can be added or adjusted using drag-and-drop.
Field Types: Mostly text or multiline text fields; severity uses a dropdown.
Example Usage: Field values are used to track the specific issue and its cause.

Bug Resolution Process

Jira Workflow: Submitting a bug in Jira activates the process.
Assignment: Team members assign themselves to resolve the issue.
Prioritization: Severity guides assignment and resolution priority.
Known Bugs: Many minor bugs are intentionally shipped with software (inexpensive to leave in).

This quiz focuses on the essential information and procedures for documenting and reporting software bugs during testing. Covering details like the test ID, environment, reproduction steps, and severity levels, it is essential for ensuring effective communication in software development. Perfect for testers and software developers alike.