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

Enhancement to dynamically use test project for "no diagnostics" automated tests #489

Open
TrevCraw opened this issue Jul 19, 2023 · 0 comments
Labels
automated tests Related to automated integration or unit tests enhancement New feature or request

Comments

@TrevCraw
Copy link
Contributor

Description:

In #483, a new test project was added which includes fake Jakarta imports in order to test the scenario where we should only be providing diagnostics when the fully qualified Jakarta package name is available as an import.

Currently, this means that any updates made to the original test project will need to be made to the second project as well. In order to avoid dual maintenance, we could dynamically retrieve the Java files from the original test project (jakarta-sample) and then modify the imports to make them fake before passing them as input to the "no-diagnostics" test.

@turkeylurkey turkeylurkey added enhancement New feature or request automated tests Related to automated integration or unit tests labels Jul 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automated tests Related to automated integration or unit tests enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants