In our project, every time we create a pull request we run some Espresso tests to check our app runs fine with the new changes. We started to see that in case of success for all the tests, the report was not generated, seeing the error Failed to render junit report. error="open ./build/sauce/saucectl-report.xml: no such file or directory" without any change in our config.yml file:
And Archiving violations report we had this warning:
Desired behavior
To grant backward compatibility the default value of allAttempts should be true, instead of false, this way the report will be generated in all the cases, success and failure, just as it was before.
Current behavior
In our project, every time we create a pull request we run some Espresso tests to check our app runs fine with the new changes. We started to see that in case of success for all the tests, the report was not generated, seeing the error
Failed to render junit report. error="open ./build/sauce/saucectl-report.xml: no such file or directory"
without any change in ourconfig.yml
file:And Archiving violations report we had this warning:
Desired behavior
To grant backward compatibility the default value of
allAttempts
should be true, instead of false, this way the report will be generated in all the cases, success and failure, just as it was before.Config to reproduce
Workaround
If we add
allAttempts: true
toartifacts
it works fine again in case of success or failure:Versions
Tested with: