-
Notifications
You must be signed in to change notification settings - Fork 4
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
Tests with dynamic data in their name are not executed #17
Comments
For those that is using ScalaTest runner (Intellij plugin included), to run a 'selected' test it is done by passing the -t specifying the test name as the test intended to be run, but in your example, I don't think it is possible for the test name to match what's being passed over. However for your CI, unless you are using -t in your configuration I don't see why your tests is being skipped. Having say so, in case you really need to log out the timestamp, you may want to use |
@uhla Thanks for the detailed information, I'll try the gradle build as you mentioned and see if I can reproduce the problem. Thanks! |
@uhla Fyi I can reproduce your problem with gradlew, I'll try digging further to see what's causing it next. |
Simplified case:
When I try to run tests using gradle, this test is not executed when using junit5 platform with scalatest engine (5.1-3.2.18). If I run the same using IntelliJ plugin runner, it's executed without issue.
I suspect this is because the different value there at test registration and then test class execution. We discovered this by accident when we noticed some tests were not running on our CI after update to this library from old junit4 runner and scalatest)
The text was updated successfully, but these errors were encountered: