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

Add a custom reporter to Cypress tests #6174

Closed
1Copenut opened this issue Aug 24, 2022 · 4 comments
Closed

Add a custom reporter to Cypress tests #6174

1Copenut opened this issue Aug 24, 2022 · 4 comments
Assignees
Labels
accessibility - automated accessibility stale-issue stale-issue-closed testing Issues or PRs that only affect tests - will not need changelog entries

Comments

@1Copenut
Copy link
Contributor

I'd like to add a reporter to our Cypress tests. I'm looking strongly at mochawesome because it works well with Cypress and gives us a way to consolidate one HTML report.

Reporter will capture passing and failing tests in a single location. Should also be able to capture a11y violations data.

@1Copenut 1Copenut added accessibility testing Issues or PRs that only affect tests - will not need changelog entries accessibility - automated labels Aug 24, 2022
@1Copenut 1Copenut self-assigned this Aug 26, 2022
@daveyholler
Copy link
Contributor

@1Copenut to update on current on-hold status

@github-actions
Copy link

👋 Hi there - this issue hasn't had any activity in 6 months. If the EUI team has not explicitly expressed that this is something on our roadmap, it's unlikely that we'll pick this issue up. We would sincerely appreciate a PR/community contribution if this is something that matters to you! If not, and there is no further activity on this issue for another 6 months (i.e. it's stale for over a year), the issue will be auto-closed.

Copy link

github-actions bot commented Dec 2, 2023

👋 Hi there - this issue hasn't had any activity in 6 months. If the EUI team has not explicitly expressed that this is something on our roadmap, it's unlikely that we'll pick this issue up. We would sincerely appreciate a PR/community contribution if this is something that matters to you! If not, and there is no further activity on this issue for another 6 months (i.e. it's stale for over a year), the issue will be auto-closed.

Copy link

❌ Per our previous message, this issue is auto-closing after having been open and inactive for a year. If you strongly feel this is still a high-priority issue, or are interested in contributing, please leave a comment or open a new issue linking to this one for context.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility - automated accessibility stale-issue stale-issue-closed testing Issues or PRs that only affect tests - will not need changelog entries
Projects
None yet
Development

No branches or pull requests

2 participants