You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know it's bad practice, and I don't know (docs don't seem to mention) if it is intended.. but I just tried junit5 for the first time in a little demo project using the java default package. It took some time to realize, but tests only seem to be picked up by the gradle test plugin, if I move them out of the default package namespace.
I could create a sample github project from it, or you tell me this is known and intended as such. :)
Regards,
Oliver
The text was updated successfully, but these errors were encountered:
I just confirmed that it is a bug by moving the AssertionsDemo class in the documentation project to the root of the classpath and then running gradle -a :documentation:clean :documentation:test. Before moving the test class, there were 79 tests found; afterwards there were only 73 tests found.
sbrannen
changed the title
Tests in default package do not get picked up
Tests in default package do not get picked up via classpath scanning
Aug 15, 2016
This commit picks up where 63c9ff4 left
off by supporting "" as the default package in ReflectionUtils.isPackage().
Furthermore, classpath scanning is now supported when "" is selected as
the base package for scanning.
Issue: #465
I know it's bad practice, and I don't know (docs don't seem to mention) if it is intended.. but I just tried junit5 for the first time in a little demo project using the java default package. It took some time to realize, but tests only seem to be picked up by the gradle test plugin, if I move them out of the default package namespace.
I could create a sample github project from it, or you tell me this is known and intended as such. :)
Regards,
Oliver
The text was updated successfully, but these errors were encountered: