Scrub skipped test issue numbers

Open
#17,235 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
testing-qa

Research direction

No files or tests are named. Start by inventorying skipped tests in the EF Core repository and checking the referenced issue numbers and skip patterns. Done means each skipped test is justified or removed, references an appropriate open issue, uses a common pattern, and has consistency checks or automation where feasible.

Written by the indexing model from the issue text.

Description

Scrub all skipped tests to:

  • Determine if it is useful to keep the test
  • If so, then make sure an open issue number is referenced, and the issue is appropriate for the test being disabled
  • Skip the test using a common pattern
    • Add API consistency tests to ensure that tests are using the correct pattern
    • Consider automating checks so that tests are flagged if they are disabled for a closed issue
Dominant language
C#
Stars
14.8k
Forks
3.4k
Avg merge
2d 5h
Merged PRs (30d)
134

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/efcore

All issues in dotnet/efcore

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.