- Mais recentes
- Mais votos
- Mais comentários
Hi hclmobiletest,
I assume you have been following the approach mentioned in the following link. Please double check that.
https://aws.amazon.com/blogs/mobile/custom-artifacts-on-aws-device-farm/
If your approach is the same, can you share run url for one of the runs so that we can investigate this.
Yes, that is the approach I was trying to follow. For example in projects/7448c707-aa1e-4cea-8e9e-47b516e8902b/runs/6ac81cff-786a-48d9-a926-4eaeac0f1320 , in the test spec, I do a echo "project_report_directory=$WORKING_DIRECTORY" >> target/classes/_config.properties which ended up setting it to. project_report_directory=/tmp/customer_artifacts_working_directoryTGBaBw. At the end of the run, my framework told me that the output had been created (test spec log line 240), but the path is /tmp/scratchOfaEGq.scratch/test-packageAiHwxW/tmp/customer_artifacts_working_directoryTGBaBw/.
It seems the framework is getting the base directory from System.getProperty("user.dir") and then appending the path which I was giving $WORKING_DIRECTORY. That is the issue. I will try to pass user.dir to testNG in the java command line and see if that will resolve this.
The problem is solved. I just need to pass -Duser.dir=$DEVICEFARM_LOG_DIR on the java command line so that the framework puts its screenshots and report content under the Log dir and it is finally getting collected with the testng result.
Conteúdo relevante
- AWS OFICIALAtualizada há 3 meses
- AWS OFICIALAtualizada há 2 meses
- AWS OFICIALAtualizada há 2 anos