Define an automated testing approach
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
The issue provides no body and names no files, tests, or entry points. Start by examining the repository structure and existing test setup, then clarify the intended automated testing approach and its acceptance criteria before making changes.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- C#
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from equilaterus/CoverScript
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
equilaterus/CoverScript#11 ·
-
MSTest support Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
NUnit support Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
XUnit support Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
equilaterus/CoverScript#6 · 1 assignee ·
All issues in equilaterus/CoverScript
Similar issues
-
Status: Waiting triage Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
nanoframework/Home#1857 ·
-
kind/bug kind/regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
unoplatform/uno.toolkit.ui#1646 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nightscout/nocturne#1379 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
elastic/esql-dotnet#47 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100