[tests] organize/consolidate/de-duplicate shared or shareable analyzer/server/linter test logic #60036
Open
1 of 2 tasks
Labels
area-devexp
For issues related to the analysis server, IDE support, linter, `dart fix`, and diagnostic messages.
P2
A bug or feature request we're likely to work on
test-technical-debt
Dealing with technical debt in the area of tests and testing
There are at least a few tasks that could go towards improving test maintenance and authoring, leading to improved velocity, less technical debt and hopefully more fun (and better coverage) when writing tests.
De-Duplication. Analyzer, Linter and Server tests have a bit of duplication. Logic that's duplicated adds maintenance and confusion when once shared logic diverges.
Unification. Besides duplication, we have many tests that test similar things but in subtly different ways. (Anecdotally, my recent language feature implementation tasks have been largely dominated by test authoring that in turn was largely dominated by answering questions of the "am I holding this right" kind.) Unification would speed up test-authoring and would have as a side-effect less test code to maintain.
@dart-lang/analyzer-team: I'm taking a look at this and will update this item with concrete proposals and ideas. In the meantime, please feel free to chime in with thoughts/ideas!
The text was updated successfully, but these errors were encountered: