Theme

Bug report template

Written by

in

Summary

Rule

Example

Title should be self-descriptive ("What?" "How behaves?" "While what conditions?").

[Vacancies]. Error page is displayed after visiting the Vacancy page and changing its status.

Bug specific should be stated on first place (ex.: reproducible only on some device type, intermittent issue, environment specific, any other unique attribute).

[Tablet] [Mobile] [RT]. Profile page is not adapting to the new layout after rotating the device.
[Intermittent] [PROD] [Companies]. Updates are not displayed on the company preview page after clicking the “Vorchau“ button.

Component name should be stated at the beginning of the title.

[Applicants]. User is not shown in the Applicants tab after applying on the publication.

Avoid using not exact phrases such as "working not appropriately", "not proper way","not per design". Try to be as specific as possible.

[PaaS]. Report is downloaded in a not proper format.

Description

  • Steps should be as specific as possible;

  • Examples of pages, profiles, vacancies, etc. that could be used for easier bug reproducing should be provided in any suitable form (URL, ID, etc.);

  • Actual and Expected results should be provided with appropriate screenshots, whenever applicable;

  • During bug creation, separate critical/major/minor bugs and create a separate bug for each issue;
    You can combine the bugs if they have the same priority. But if the priority is different – please create 2 or more bugs.

  • If during retesting the bug, the issues described initially are fixed, close the bug, and for all new issues that appeared after the fix and weren’t described in the bug initially create a NEW bug.

Bug template

Filed

What to fill

Filed

What to fill

Project

ROCKEN-TALENT (RT)

Issue type

Bug

Summary

A brief one-line summary of the issue.
Summary field name should be filled according template:
[Area name] <Problem short and concrete description>

Component

<Component’s name> select from the dropdown

Description

Description field should be filled as in following template:

Preconditions:

REPLACE the TEXT with needed configuration, if applicable.

Steps to reproduce:

  1. Step_1.

  2. Step_2.

  3. Step_3.

Actual result:

Clear description of what actually happened.

See attached screenshot for more details.

<Screenshot>

Expected result:

Clear description of what should have been happened.

See attached design for more details.

<Screenshot> / <link to the design>

Additional information:

REPLACE the TEXT with Additional information, if applicable.

Priority

The degree of importance for the business to resolve the defect. It is driven
by business value and indicates how soon the defect should be fixed.

Labels

Choose “Rocken“ from the drop down. The label indicates the bug is related to some component. For each project, the list of labels is specific.

Environment

one of the (STG, PROD) + version (for NA https://api.rocken-talent.cheitgroup.com/api/v1/version)

Attachment

If you can supplement your bug report with a picture that shows the
problem, or a score that helps others reproduce, fix and verify the problem
quickly, attach these files to the bug report. The attached files can be as
follows: pictures, video-recording, other files types, if needed.

Linked Issues

<link to the related issue>

Assignee

The person whom the bug is assigned to (backend issues – BE/Dev Lead,
Frontend issues – FE Lead)

Epic Link

Contains a link to Epic in accordance with overall structure of epics on the
project.

Sprint

optional

QA Scope

<testing scope>

Comments

Leave a Reply

More posts