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

Need high-level test #1003

Closed
mickaelistria opened this issue Nov 29, 2024 · 2 comments
Closed

Need high-level test #1003

mickaelistria opened this issue Nov 29, 2024 · 2 comments

Comments

@mickaelistria
Copy link

We need some extra higher automated tests to prevent from regressions as we've seen for the last days.

  • Import a project with various sources (we can put anything we have in mind here)
  • Build and verify it has no errors, or only expected errors (covers the build)
  • Opens every file in the editor, verify editors open fine (covers the Javac->DOM translation)
  • From the DOM, navigate the tree and call all possible resolveBindings (covers JavacBindingResolver)
@datho7561
Copy link

Build and verify it has no errors, or only expected errors (covers the build)

#1017 covers this, if someone needs to make another similar test in the future, feel free to refer to it

@mickaelistria
Copy link
Author

While I still think the even bigger tests would be profitable, I hardly imagine anyone spending time to write such a test at the moment. I hope that if we add new tests for each new strange case we identify that's not already covered, we'll end up having a good enough coverage.
So I'm closing it; but if anyone wants to design a really powerful acceptance test scenario, that would still be very welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants