-
Notifications
You must be signed in to change notification settings - Fork 212
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
kt_jvm_test should infer the test_class if unspecified. #150
Comments
kt_jvm_test
should infer the test_class
if unspecified.
Is it ok to just use the package name after translation directly ? My gut feel is that a normalising heuristic would be needed otherwise the java packages would need names like |
Sadly it'll need normalizing. Thankfully, the normalizing heuristic would probably would walking backwards to The nice thing, is that this is an inferred default, so it can be wrong - you'll just end up specifying manually if you use a non-standard pattern for folder structure. I'm not sure if it's possible to ingest the source files either, but if so, both java and kotlin declare "package" so that might also be a possibility. |
I think this is still broken, as I'm having to still specify a |
Seems broken. On my side I'm getting similar issue.
|
+1 broken for me as well. My failure didn't even include the class name:
@cgruber can you re-open this issue please? |
+1 |
This can happen in my experience if the package name is left out from the test kt file |
If the rule is named
FooTest
and the test file isFooTest.java
orFooTest.kt
, and thetest_class
is unspecified, the test rule should just work out that the test_class ismy.package.FooTest
.The text was updated successfully, but these errors were encountered: