-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Proposal: Integrate Dashboard test results with outside services. #981
Comments
Hipchat would be great |
Conversations in Gitter surrounding integrations:
|
Would really love it if these could be implemented as a post-run/post-upload event so we can write our own service integration plugins. |
This comment has been minimized.
This comment has been minimized.
I mean, most of the major ones, probably, but it'd be nice to be able to write my own hooks for services outside that ecosystem, or even totally custom automation, around the results of these tests. |
@jennifer-shehane I would be happy to contribute GitHub and Jira integrations. And due Atlassian Connect, the Jira work would also cover Bitbucket integration. I think this would help with #1173. I'm familiar with the APIs, and would love to help. 🙂 |
Cucumber integration? |
@acthilina There is a cucumber plugin that integrates with Cypress you may want to check out. https://docs.cypress.io/plugins/ |
Thank you @jennifer-shehane , If you have more info, please send my way. :-) |
Gitlab please! |
@soccer99 Thanks for the suggestion. Gitlab currently isn't on our immediate integrations roadmap. But it might be in the future, specially if there is user demand for it. We'd be glad to hear what level of integration you're looking for. |
Before doing too many custom integrations I’d recommend implementing outbound webhooks; they can be used to integrate just about anything. |
We're looking for a possible integration with confluence that prints out bar charts, pass/fail, etc. |
@Nate-Watts feel free to elaborate further on the Confluence integration for the sake of documentation. We might integrate with the Atlassian stack down the line, and it would be nice to have your feedback in our considerations. Thank you. |
Would love to see this. I agree with @gscott on outbound webhooks. If those exist, almost anything should be able to be wired up, then the more specific integrations can come in the future (potentially built on that same webhook system). |
How we integrate Test-link to cypress? :( |
@jennifer-shehane - is the idea with this proposal that Cypress itself will be able to integrate with all (or at least some) of the listed services? Or is this the Cypress Dashboard service integrating with the listed services? I'm hoping for the former, though I'd understand the latter. |
@Knaledge The scope of this issue is for the Dashboard Service (any test using --recording), otherwise we don't have the data to integrate or know when to trigger notifications. There is a separate issue regarding native notifications that could be triggered when running the Cypress test runner by itself here: #2145 |
@bdim Could you open a pull request to add this plugin to our documentation? Thanks! Instructions here. |
@jennifer-shehane Here it is cypress-io/cypress-documentation#1444. Thanks! :) |
PagerDuty please :) |
integration with qTest https://www.qasymphony.com/ |
Hi all! We're continuing to make progress on adding GitHub integration to the Cypress Dashboard and would love to get some hands-on user feedback at this point. Does anyone have a few minutes to talk through the designs with me? You'd get a chance to try out this new integration in your own project, and you'll get to keep access to the feature afterwards! Please leave a comment here, or email me directly if you're interested. Thank you! |
I'd like to try it out!
…On Fri, Mar 29, 2019, 11:25 AM Jeff Tucker ***@***.***> wrote:
Hi all! We're continuing to make progress on adding GitHub integration to
the Cypress Dashboard and would love to get some hands-on user feedback at
this point. Does anyone have a few minutes to talk through the designs with
me? You'd get a chance to try out this new integration in your own project,
and you'll get to keep access to the feature afterwards!
Please leave a comment here, or email me directly if you're interested.
Thank you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#981 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AkqCPo7_fZA5S59dXOAWKX-6hEUpFrnSks5vbkyTgaJpZM4QvSL->
.
|
Same here!
On Fri, Mar 29, 2019, 20:45 MangoVerde-con-Sal <notifications@github.com>
wrote:
… I'd like to try it out!
On Fri, Mar 29, 2019, 11:25 AM Jeff Tucker ***@***.***>
wrote:
> Hi all! We're continuing to make progress on adding GitHub integration to
> the Cypress Dashboard and would love to get some hands-on user feedback
at
> this point. Does anyone have a few minutes to talk through the designs
with
> me? You'd get a chance to try out this new integration in your own
project,
> and you'll get to keep access to the feature afterwards!
>
> Please leave a comment here, or email me directly if you're interested.
> Thank you!
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#981 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AkqCPo7_fZA5S59dXOAWKX-6hEUpFrnSks5vbkyTgaJpZM4QvSL-
>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#981 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB6QhL1qXO_8Jzc09RJ120AyP0YySRDKks5vblE9gaJpZM4QvSL->
.
|
@trydionel Same here! |
Awesome, thank you so much @Nate-Watts, @nir0s, @prescottprue! Just to confirm, you'll need to have 1) a project recording to the Cypress Dashboard, and 2) the repo for this project hosted on github.com, either publicly or privately. If you meet those criteria, please grab a time slot on my calendar: https://calendly.com/trydionel/github-integration-research?month=2019-04 Looking forward to talking soon! |
@trydionel would also love to hop on this beta, we meet the criteria |
@freedomflyer Sure thing! Can you get in touch with me at the email listed on my GitHub profile? |
+1 to the webhooks, it would be great if we can have webhooks with information such as -
|
We use Flowdock for our company chat, so this integration would be useful for us. |
👋 Hi everyone, we're excited to release GitHub Integration for the Cypress Dashboard today. The Cypress GitHub App tightly integrates with your workflow via commit status checks and pull-request comments. Read all about it below, and let us know what you think (@ me). Blog post: https://cypress.io/blog/2019/07/29/github-integration-for-the-cypress-dashboard/ |
Awesome! :-) Please do GitLab next. :-) |
Love the integration, but the experience of using it with Slack needs some love. Right now, there are too many images being used in the commit reply, and it Slack, the message is basically a big block of image links. I like to suggest the use of emoji over the icons that are shown there and the removal of the header image. |
It's great to be able to see the Cypress test results on the PR page but as @aequasi mentioned, it makes the integration very noisy in slack and pretty much unusable. |
Hey @aequasi, @thomaspicquet, Yea, that's a bit rough 😬 Would you mind to answer some questions about your workflow?
Thanks for the feedback! PS: If you have any other feedback for the Cypress Dashboard, or are just curious about what we're working on, please check out our updated roadmap at https://portal.productboard.com/cypress-io/1-cypress-dashboard/tabs/1-under-consideration. |
Hey @trydionel, We use Slack for a lot of things and we have a channel for our CI with:
It's nice to see the Cypress PR message and I'd like to keep that over the Checks tab on github but the message is really big and not really useful when it gets to Slack, unfortunately. |
Cool, I've added your feedback to our product backlog. Thanks for the info! Also, if you find the PR comments too noisy, you can turn them off independently of the commit status checks. See our documentation. |
@jennifer-shehane @amirrustam @trydionel +1 for sending cypress run reports to designated emails. It will be great if we can have summarized results of cypress run (from dashboard) being delivered to specific email addresses. Raising a red alarm in case of any failures or sending a green report in case tests passed. |
You can express interest and see progress for this feature on our Roadmap from our Dashboard's product board here: https://portal.productboard.com/cypress-io/1-cypress-dashboard (Look for the card with your desired integration or I will be closing this issue and closing it to all comments since this is related to our Dashboard. All related work for Dashboard features is handled in that ProductBoard and will be addressed by the Dashboard team directly when you comment there. We have already noted the initial comments from this issue there. Please refer all future comments there. Thank you. |
Slack integration is now available within our Cypress Dashboard. It allows you to see your Cypress test results directly in your teams’ Slack channels. Please read our Slack Integration docs to get started. |
We'd like to have test results integrate with third party services like:
GitHub (DONE)Submit idea
if you don't see it)Our Dashboard Service knows when tests fail, it has details about a user's recorded CI run. When certain conditions are met, it can notify other integrated services and do things like:
The Dashboard should likely have a UI interface allowing the user to set what integrations they would like and what data they would like sent (on project? on organization?)
This proposal is a WIP currently, so we'd love to hear from the community on what you'd like to see.
You can express interest and see progress for this feature on our Roadmap from our Dashboard's product board here: https://portal.productboard.com/cypress-io/1-cypress-dashboard (Look for the card with your desired integration or
Submit idea
if you don't see it)The text was updated successfully, but these errors were encountered: