IntelliTect / IntelliTect/TestTools.TestFramework
Create an analyzer
- Langage dominant
- C#
- Étoiles
- 1
- Forks
- 1
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
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()
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
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.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- csharp
- Domaine
- testing-qa, tooling
- Type d'issue
- Fonctionnalité
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- Active
- Clarté
- Plutôt claire
- Accessibilité débutants
- 48/100