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
When using the AndroidX Orchestrator (I have not tested the Android one, but assume it will be the same) some tests are skipped if the length of the classname + method name is too long
Steps to Reproduce
Create a test within a class, where the class name (including the package) and the method name total over 250 characters.
Expected Results
Test runs correctly, OR an error is printed that directs the developer to adjust this
Actual Results
This test will not run (but it's not marked as ignored, etc.)
I have a feeling this is because the Orchestrators create a directory on the device for the ADB output, and thusly if the method/class name is too long, it overflows the file-name-length constraints on the particular device. It is, however, unfortunate, that no relating error is ever bubbled up to the developer.
The text was updated successfully, but these errors were encountered:
Description
When using the AndroidX Orchestrator (I have not tested the Android one, but assume it will be the same) some tests are skipped if the length of the classname + method name is too long
Steps to Reproduce
Create a test within a class, where the class name (including the package) and the method name total over 250 characters.
Expected Results
Test runs correctly, OR an error is printed that directs the developer to adjust this
Actual Results
This test will not run (but it's not marked as ignored, etc.)
I have a feeling this is because the Orchestrators create a directory on the device for the ADB output, and thusly if the method/class name is too long, it overflows the file-name-length constraints on the particular device. It is, however, unfortunate, that no relating error is ever bubbled up to the developer.
The text was updated successfully, but these errors were encountered: