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'm noticing that the j2objcTestDebug Gradle step which calls the testJ2objc script fails if I have any classes in my test folder (mocks and helper classes for example) which have zero test methods. Would be great if this Gradle step / test script skipped over classes that have zero test methods rather than failing the build.
I'm aware that there is a workaround which is to add include and exclude patterns in my SharedCode/build.gradle file for classes that are to be tested or not. The problem with this is that it's one more part of the build process to remember and maintain and could involuntarily lead to test classes being ignored that match the exclude pattern or don't match the include pattern.
(My tests btw are written in the JUnit 4 syntax.)
The text was updated successfully, but these errors were encountered:
I'm noticing that the
j2objcTestDebug
Gradle step which calls thetestJ2objc
script fails if I have any classes in my test folder (mocks and helper classes for example) which have zero test methods. Would be great if this Gradle step / test script skipped over classes that have zero test methods rather than failing the build.I'm aware that there is a workaround which is to add
include
andexclude
patterns in mySharedCode/build.gradle
file for classes that are to be tested or not. The problem with this is that it's one more part of the build process to remember and maintain and could involuntarily lead to test classes being ignored that match the exclude pattern or don't match the include pattern.(My tests btw are written in the JUnit 4 syntax.)
The text was updated successfully, but these errors were encountered: