Skip to content

Installing cypress-multi-reporters again#4088

Merged
olemartinorg merged 1 commit intomainfrom
chore/cypress-multi-reporters
Mar 30, 2026
Merged

Installing cypress-multi-reporters again#4088
olemartinorg merged 1 commit intomainfrom
chore/cypress-multi-reporters

Conversation

@olemartinorg
Copy link
Copy Markdown
Contributor

@olemartinorg olemartinorg commented Mar 30, 2026

Description

I removed cypress-multi-reporters in #4024, but I recently found out what it's actually for - our cy:parallel script in package.json. Specifically, the cypress-parallel job needs a way to collate reports from multiple runners, and it looks for cypress-multi-reporters as a runtime dependency.

Related Issue(s)

  • closes #{issue number}

Verification/QA

  • Manual functionality testing
    • I have tested these changes manually
    • Creator of the original issue (or service owner) has been contacted for manual testing (or will be contacted when released in alpha)
    • No testing done/necessary
  • Automated tests
    • Unit test(s) have been added/updated
    • Cypress E2E test(s) have been added/updated
    • No automatic tests are needed here (no functional changes/additions)
    • I want someone to help me make some tests
  • UU/WCAG (follow these guidelines until we have our own)
    • I have tested with a screen reader/keyboard navigation/automated wcag validator
    • No testing done/necessary (no DOM/visual changes)
    • I want someone to help me perform accessibility testing
  • User documentation @ altinn-studio-docs
    • Has been added/updated
    • No functionality has been changed/added, so no documentation is needed
    • I will do that later/have created an issue
  • Support in Altinn Studio
    • Issue(s) created for support in Studio
    • This change/feature does not require any changes to Altinn Studio
  • Sprint board
    • The original issue (or this PR itself) has been added to the Team Apps project and to the current sprint board
    • I don't have permissions to do that, please help me out
  • Labels
    • I have added a kind/* and backport* label to this PR for proper release notes grouping
    • I don't have permissions to add labels, please help me out

Summary by CodeRabbit

  • Chores
    • Updated development tooling dependencies to support enhanced test reporting capabilities.

@olemartinorg olemartinorg added ignore-for-release Pull requests to be ignored in release notes backport-ignore This PR is a new feature and should not be cherry-picked onto release branches labels Mar 30, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Mar 30, 2026

📝 Walkthrough

Walkthrough

Added cypress-multi-reporters (version 2.0.5) as a dev dependency in package.json. No other configurations, scripts, or dependencies were modified.

Changes

Cohort / File(s) Summary
Dependency Addition
package.json
Added cypress-multi-reporters dev dependency (v2.0.5).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description check ✅ Passed The description includes a detailed explanation of why the dependency is being reinstalled and its purpose, follows the template structure, and properly addresses the verification checklist.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check ✅ Passed The title accurately and concisely describes the main change: reintroducing the cypress-multi-reporters dependency that was previously removed.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/cypress-multi-reporters

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@package.json`:
- Line 73: package.json added cypress-multi-reporters but cypress.config.js
still sets reporter: 'junit', so the multi-reporter package isn't used; update
cypress.config.js to set reporter to 'cypress-multi-reporters' (or require its
module) and add reporterOptions to configure the underlying reporters (e.g.,
include 'junit' as one reporter and any output paths/merge/namespace options) so
test results are collated correctly; locate the reporter setting in
cypress.config.js and replace reporter: 'junit' with reporter:
'cypress-multi-reporters' plus an appropriate reporterOptions object.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 7f7a1ca7-4a0c-4241-87c3-e50b3ef97fd8

📥 Commits

Reviewing files that changed from the base of the PR and between 3ca3cd8 and bcb1606.

⛔ Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (1)
  • package.json

@sonarqubecloud
Copy link
Copy Markdown

@olemartinorg olemartinorg changed the title Installing cypress-multi-reporters again Installing cypress-multi-reporters again Mar 30, 2026
@olemartinorg olemartinorg merged commit 4df0d6f into main Mar 30, 2026
16 of 18 checks passed
@olemartinorg olemartinorg deleted the chore/cypress-multi-reporters branch March 30, 2026 13:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-ignore This PR is a new feature and should not be cherry-picked onto release branches ignore-for-release Pull requests to be ignored in release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants