Thank you for sharing details of the current scenario you need to cover.
You are correct that the executing a mobile test as step is not an out-of-the-box feature in a mobile project and the only approach you can go for is within a coded step. This kind of limitation is because of the specifics of running the tests on a mobile device - and what I mean by specifics is the way the mobile applications are being started for the test automation.
Having that said, it will be important to sort out what is the exact scenario for executing a mobile test from within another mobile test. Possibly, the coded step should work, if the test called from the coded step should run against different application. Otherwise, if it should run against the same app, it may be not started in the desired state.
So to be able to find out what could possibly go wrong, there will be some additional details required to analyze the case. Thus, I will appreciate if you can go through the below topics and share your input on these:
- what is supposed the test called from the coded step to do?
- does it start a new application on the device?
- when you execute the coded step, what is being executed on the device?
- do you see the target application starting at all?
- if yes, does it start in the desired state?
- any further details related to the coded step execution will be helpful for us to identify what could be causing the failing exit code.
In addition to all of these, I noticed that in the command listed in the coded step there is a missing file extension for the test - as per the documentation
argument should contain the file extension like this:
I am not sure if this will change the misbehavior you observe. However, if this is not the missing piece and you need additional assistance, I will be looking forward to hearing back from you more about the requested details.
Thank you in advance for your time and cooperation.