Status Update
No update yet.
Comments
sl...@google.com
pr...@gmail.com
As a general note, what you're checking makes little sense - onAttachFragment is called as fragments move through their lifecycle methods (specifically, right after onAttach() is called on the fragment) and is therefore likely to be called while FragmentTransactions are being processed - if you have multiple commit()s in flight, the state you get back in onAttachFragment will certainly not be the final state the FragmentManager will be when all of the FragmentTransactions are executed, making this a bit of a meaningless check.
That being said, this is caused by the mechanism used to kick off transitions when reordering is not allowed, which is being reworked in
As a workaround, you can use setReorderingAllowed(true) on your transaction, which will allow your example project to work correctly.
nk...@google.com
This has been fixed internally and will be avilable in Fragment 1.3.0-alpha08.
Note: this fix relies on using the
Description
Version used: Espresso(3.0.1), Runner and Rules (1.0.1)
What steps will reproduce the problem?
1. Install orchestrator-1.0.1.apk and test-services-1.0.1.apk
2. Build App under Test and Test apk and install on device
3. execute below command for Test Orchestration
adb shell 'CLASSPATH=$(pm path android.support.test.services) app_process / \android.support.test.services.shellexecutor.ShellMain am instrument -w -e \
targetInstrumentation com.package.test/com.package.espressoTests.Instrumentation \android.support.test.orchestrator/.AndroidTestOrchestrator'
After executing above command, it starts execution on device (Samsung Marshmallow) with below log output
MdfppReflectionUtils isMdfEnforced encountered an exception. Cause: java.lang.UnsatisfiedLinkError: No implementation found for boolean com.samsung.android.security.CCManager.isMdfEnforced() (tried Java_com_samsung_android_security_CCManager_isMdfEnforced and Java_com_samsung_android_security_CCManager_isMdfEnforced__) Message: null
MdfppReflectionUtils isMdfEnforced encountered an exception. Cause: java.lang.UnsatisfiedLinkError: No implementation found for boolean com.samsung.android.security.CCManager.isMdfEnforced() (tried Java_com_samsung_android_security_CCManager_isMdfEnforced and Java_com_samsung_android_security_CCManager_isMdfEnforced__) Message: null
If we execute only one/few test case, it shows below output when execution is complete
-Final result — OK (0 tests)
If we execute batch of tests, execution stopped because of process crash due to out of memory.
How are you running your tests (via Android Studio, Gradle, adb, etc.)?
Using adb command
What is the expected output? What do you see instead?
Expected output is to continue execution of next test if there is any crash due to memory issue or due to application crash due to some other reason. I have attached few screenshots which shows memory usage when process crashed and Instrumentation file. Please let me know if you need any other details.