IntelliTect / IntelliTect/TestTools.TestFramework
Create an analyzer
- Vorherrschende Sprache
- C#
- Sterne
- 1
- Forks
- 1
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
Been thinking about doing this for a couple of years now. Some things that would be good to have:
- Classes implementing ITestBlock but that don't have an Execute() method.
- TestBlocks with an async Task signature but are added via AddTestBlock
- Using .Build().Execute() instead of .Build().ExecuteAsync()
Beitragsleitfaden
Rechercherichtung
Start by locating ITestBlock, Execute, ExecuteAsync, AddTestBlock, and Build in the repository, then review how tests and diagnostics are organized. Define analyzer coverage for the three listed patterns and verify that each is reported with focused tests; done means all requested misuse cases are detected without flagging valid usage.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- csharp
- Bereich
- testing-qa, tooling
- Issue-Typ
- Feature
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Aktiv
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 48/100