Bug 41911 – Mark and skip flaky test cases

Bug 41911 - Mark and skip flaky test cases


Summary:	Mark and skip flaky test cases

Status:	NEW

Product:	UCS Test
Classification:	Unclassified
Component:	General
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-08-04 06:18 CEST by Stefan Gohmann
Modified:	2018-04-14 13:47 CEST (History)
CC List:	1 user (show)

See Also:	40709
What kind of report is it?:	Development Internal
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Stefan Gohmann

2016-08-04 06:18:46 CEST

We should add a new tag which defines test cases which fail from time to time. My suggestion is to call the tag 'flaky'.

It would be great if it we make it configurable via Jenkins if the flaky tests are executed. The flaky test cases should be skipped by default by our daily test cases.

Comment 1 Florian Best

2016-08-15 11:53:39 CEST

This feature exists in pytest and is mentioned in Bug #40709.