You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to make it easy for users to publish their results to external services. Allowing users to specify a URL to send results to should help.
I'm fully aware that this is a fragile solution - if the server is unavaible there is no way to resend the messages - cucumber would have to be run again.
We will also provide guidelines about alternative, more robust mechanisms to publish results, such as:
Write messages to a file
Use cURL to publish after cucumber is done
Write messages to the CI server's "artifacts" directory and have a process somewhere else that can download them
Okay I get this now I have seen Aslak's Smartbear talk. Could be a little tricky as it would be different implementations for Node vs browser. I'll take a look when I get past this messages/CCK stuff.
We want to make it easy for users to publish their results to external services. Allowing users to specify a URL to send results to should help.
I'm fully aware that this is a fragile solution - if the server is unavaible there is no way to resend the messages - cucumber would have to be run again.
We will also provide guidelines about alternative, more robust mechanisms to publish results, such as:
I've implemented this for cucumber-ruby in cucumber/cucumber-ruby#1395
Anyone wants to take a crack at this?
The text was updated successfully, but these errors were encountered: