Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document guidelines on how to handle flaky tests #12584

Closed
koevskinikola opened this issue Apr 27, 2023 · 0 comments · Fixed by #12583
Closed

Document guidelines on how to handle flaky tests #12584

koevskinikola opened this issue Apr 27, 2023 · 0 comments · Fixed by #12583
Assignees
@koevskinikola @remcowesterhoud
Labels
kind/documentation Categorizes an issue or PR as documentation related version:8.3.0-alpha2 Marks an issue as being completely or in parts released in 8.3.0-alpha2 version:8.3.0 Marks an issue as being completely or in parts released in 8.3.0

Comments

@koevskinikola
Copy link
Member

koevskinikola commented Apr 27, 2023 •
edited

Description

Add a guide on what to do when a flaky test is encountered. The guide should enable contributors to make progress when flaky tests occur in their contributions.

This was an action derived from one of the ZPA team's recent retros.
@koevskinikola koevskinikola added the kind/documentation Categorizes an issue or PR as documentation related label Apr 27, 2023
@koevskinikola koevskinikola self-assigned this Apr 27, 2023
@koevskinikola koevskinikola mentioned this issue Apr 27, 2023
Merged
14 tasks
zeebe-bors-camunda bot added a commit that referenced this issue Apr 28, 2023
@zeebe-bors-camunda @koevskinikola
merge: #12583
e19e033 
12583: docs: document flaky test handling r=remcowesterhoud a=koevskinikola

## Description

Add a guide on what to do when a flaky test is encountered. The guide is included in the ci.md section of our developer docs. This section is also linked inside our CONTRIBUTING.md guide to ensure that any contributors are aware of what to do in such an occurrence.

## Related issues

This was an action derived from one of the ZPA team's recent retros.

closes #12584



Co-authored-by: Nikola Koevski <nikola.koevski@camunda.com>
zeebe-bors-camunda bot added a commit that referenced this issue May 3, 2023
@zeebe-bors-camunda @koevskinikola
merge: #12583
edd0277 
12583: docs: document flaky test handling r=remcowesterhoud a=koevskinikola

## Description

Add a guide on what to do when a flaky test is encountered. The guide is included in the ci.md section of our developer docs. This section is also linked inside our CONTRIBUTING.md guide to ensure that any contributors are aware of what to do in such an occurrence.

## Related issues

This was an action derived from one of the ZPA team's recent retros.

closes #12584



Co-authored-by: Nikola Koevski <nikola.koevski@camunda.com>
@lenaschoenburg lenaschoenburg added the version:8.3.0-alpha2 Marks an issue as being completely or in parts released in 8.3.0-alpha2 label Jun 7, 2023
@megglos megglos added the version:8.3.0 Marks an issue as being completely or in parts released in 8.3.0 label Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@koevskinikola koevskinikola

@remcowesterhoud remcowesterhoud

Labels
kind/documentation Categorizes an issue or PR as documentation related version:8.3.0-alpha2 Marks an issue as being completely or in parts released in 8.3.0-alpha2 version:8.3.0 Marks an issue as being completely or in parts released in 8.3.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

docs: document flaky test handling camunda/camunda
4 participants
@megglos @lenaschoenburg @koevskinikola @remcowesterhoud