So calabash is generating a nice html report when the tests pass or fail, with the addition of a few simple commands (–format ‘Calabash::Formatters::Html’ --out index.html).
I would like to see it integrated to calabash step, just like it happens with Junit tests, and also to get automatically attached to the build.
2 Likes
Hi,
So the request is for the Calabash steps, to add the HTML format flag?
Other than that, this should be possible with http://devcenter.bitrise.io/tips-and-tricks/attach-any-file-to-build/ if I understand correctly what you want to do - correct me if I missed something, and thank you for the #feature-requests ! 
1 Like
The request is to add parameters in the run command for the report to be generated, then, get the generated .html report and deploy it.
as it is now it just executes the run command:
Running calabash-android test…
$ bundle “exec” “calabash-android” “run” “/bitrise/deploy/app-beta-debug.apk”
should be more like this
Running calabash-android test…
$ bundle “exec” “calabash-android” “run” “/bitrise/deploy/app-beta-debug.apk” “–format’Calabash::Formatters::Html’” “–out index.html”
In order to deploy should be this solution:
http://devcenter.bitrise.io/tips-and-tricks/attach-any-file-to-build/
2 Likes
Makes sense, thank you for the details!
@godreikrisztian can you please have a look and schedule this?
2 Likes
It’s assigned to @godreikrisztian, but he’s off today - I’ll bump this to the top of his task list, so he’ll start with this on Monday most likely.
1 Like
Thanks very much! 
1 Like
Any news please?
Hi @lararufflecoles,
we released a new version (1.2.0) of Calabash Android UI test step.
The step got a new input: additional_options - Additional options for calabash-android run call.
You can use this input to specify --format and any other flags you want.
The step will be available in the steplib in ~20mins.
The iOS version is coming soon.
3 Likes
Looks like all is working for Android, yay! 
1 Like
Please could you hold off for now, just waiting to hear from the iOS team.
Sure, removed the auto close for now.
Hi there,
We tried using the “Additional options for cucumber call”, encountered below error -
Running cucumber test…
$ bundle “exec” “cucumber” “–format” “html” “–out” “/Users/vagrant/deploy/calabash-android_report.html”
cucumber failed, error: exit status 1
| |
±–±--------------------------------------------------------------±---------+
| x | calabash-ios-uitest (exit code: 1) | 504 sec |
±–±--------------------------------------------------------------±---------+
| Issue tracker: …ithub.com/bitrise-steplib/steps-calabash-ios-uitest/issues |
| Source: https://github.com/bitrise-steplib/steps-calabash-ios-uitest |
±–±--------------------------------------------------------------±---------+
We are struggling to find out what “exit code: 1” really means, can you please investigate this issue and let us know of we are doing something wrong here.
Regards,
Sowmya
Hi @sowmyahebbar,
when the --output flag is set, cucumber does not print the log to the stdout, instead it writes to the specified output file.
Your output file should be in the BITRISE_DEPLOY_DIR (/Users/vagrant/deploy/). If you have deploy-to-bitrise-io step after the calabash-ios step, the log file should be attached to your build and you can check it on your build’s page on bitrise.io.
I scheduled to print the log file’s content, if cucumber fails.
1 Like
Hey @sowmyahebbar! 
The new release of this step now prints error messages even if --out flag passed to the command. 
You can update your calabash-ios-uitest to the latest, and now you will see the error. 
1 Like
@sowmyahebbar did you try the latest version (see the two comments above)? Did you still have an issue with it, or can we close this #feature-request ?