Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

create an in-memory rule test harness #58521

Closed
Tracked by #58520
pq opened this issue Sep 28, 2021 · 0 comments · Fixed by dart-lang/linter#2975
Closed
Tracked by #58520

create an in-memory rule test harness #58521

pq opened this issue Sep 28, 2021 · 0 comments · Fixed by dart-lang/linter#2975
Labels
analyzer-linter Issues with the analyzer's support for the linter package area-analyzer Use area-analyzer for Dart analyzer issues, including the analysis server and code completion. type-task A well-defined stand-alone task type-test

Comments

@pq
Copy link
Member

pq commented Sep 28, 2021

See: #58520.

Like in server, this should support:

  • multiple compilation units,
  • package dependencies, and
  • assertion of the presence (or absence) of diagnostics

I'm inclined to make something that borrows from AbstractSingleUnitTest (though probably not using reflective tests). Input here is welcome.

/cc @bwilkerson

@pq pq added type-test type-task A well-defined stand-alone task labels Sep 28, 2021
@devoncarew devoncarew added analyzer-linter Issues with the analyzer's support for the linter package area-analyzer Use area-analyzer for Dart analyzer issues, including the analysis server and code completion. labels Nov 19, 2024
@devoncarew devoncarew transferred this issue from dart-lang/linter Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
analyzer-linter Issues with the analyzer's support for the linter package area-analyzer Use area-analyzer for Dart analyzer issues, including the analysis server and code completion. type-task A well-defined stand-alone task type-test
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants