Skip to content

Identify and mark or fix potentially flaky tests #2510

@snyrting6github

Description

@snyrting6github

I've made a start on marking potentially flaky tests. These are tests which reference existing resources outside of those created by the tests themselves. While they are likely to be harmless (I can't see the octokit organisation going away soon for example), we should really be testing in pure isolation if possible.

I have created (in an upcoming PR) an attribute for doing this so we can identify them in the future more easily:
[PotentiallyFlakyTest]

These types of tests should be marked as potentially flaky or fixed.

Metadata

Metadata

Assignees

Labels

Type: MaintenanceAny dependency, housekeeping, and clean up Issue or PR

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions