Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow sending message output to a HTTP(S) URL #1296

Closed
aslakhellesoy opened this issue Mar 6, 2020 · 3 comments
Closed

Allow sending message output to a HTTP(S) URL #1296

aslakhellesoy opened this issue Mar 6, 2020 · 3 comments

Comments

@aslakhellesoy
Copy link
Contributor

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

I've implemented this for cucumber-ruby in cucumber/cucumber-ruby#1395

Anyone wants to take a crack at this?

@charlierudolph
Copy link
Member

Is this really something we should have built into the tool? Seems simple enough to create a tiny script that runs after the tests finish

@davidjgoss
Copy link
Contributor

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.

@davidjgoss
Copy link
Contributor

Closing as dup of newer #1423

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants