Skip to content

Bring back some disabled ScalaTest tests #14712

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

Closed
odersky opened this issue Mar 19, 2022 · 0 comments · Fixed by #14767
Closed

Bring back some disabled ScalaTest tests #14712

odersky opened this issue Mar 19, 2022 · 0 comments · Fixed by #14767
Assignees

Comments

@odersky
Copy link
Contributor

odersky commented Mar 19, 2022

Compiler version

3.1.3-RC2

Description

I also had to disable in #14695 two scalatest tests: ExpectationsSpec and DirectExpectationsSpec. These were test suites containing tests that checked the precise error message output of the dotty compiler. IMO such tests should never be in a regression test suite for the community build, since they essentially lock in current behavior. We do want tests about error messages of course, but these should be compiler tests that can easily be changed if the compiler's error diagnostics improve.

Not knowing scalatest. I was not able to figure out from the diagnostics which particular tests broke in the two suites, so I disabled them wholesale. It would be good to bring back those tests in ExpectationsSpec and DirectExpectationsSpec of scalatest that do not depend on specific error diagnostics of dotc.

@nicolasstucki nicolasstucki self-assigned this Mar 21, 2022
nicolasstucki added a commit to dotty-staging/dotty that referenced this issue Mar 24, 2022
We only need to disable the tests that involve getMessage on
a fact that was produced by explicitly compiling a String.

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

Successfully merging a pull request may close this issue.

2 participants