Skip to content

Conversation

@jdamore-linode
Copy link
Contributor

@jdamore-linode jdamore-linode commented Jul 31, 2025

Description 📝

For the past few months, the Cypress test results that get posted in Slack and on GitHub PRs has been missing the name of the tests that are failing, only showing the group the test belongs in instead.

This was triggered by a change in our JUnit output made as part of our reporting improvements in #11795; specifically, we changed the JUnit report to always be generated using "Jenkins mode" which changed the way that test case names were output in our XML.

Changes 🔄

  • Use JUnit test case "name" field instead of "classname" when generating test result summaries

Scope 🚢

Upon production release, changes in this PR will be visible to:

  • All customers
  • Some customers (e.g. in Beta or Limited Availability)
  • No customers / Not applicable

Target release date 🗓️

N/A. Assuming there are no objections, this can be merged whenever is convenient.

Preview 📷

Before After
Screenshot 2025-08-01 at 10 33 58 AM Screenshot 2025-08-01 at 10 33 43 AM

How to test 🧪

Verification steps

We can rely on CI for this.

Confirm that the PR comment posted by Linode bot includes the name(s) of the tests that fail.

Author Checklists

As an Author, to speed up the review process, I considered 🤔

👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support


  • I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

  • All tests and CI checks are passing
  • TypeScript compilation succeeded without errors
  • Code passes all linting rules

@jdamore-linode jdamore-linode self-assigned this Jul 31, 2025
@jdamore-linode jdamore-linode changed the title fix: [M3-10142] - Fix Cypress test summary missing test name fix: [M3-10140] - Fix Cypress test summary missing test name Jul 31, 2025
@jdamore-linode jdamore-linode changed the title fix: [M3-10140] - Fix Cypress test summary missing test name fix: [M3-10410] - Fix Cypress test summary missing test name Jul 31, 2025
@jdamore-linode jdamore-linode marked this pull request as ready for review August 1, 2025 14:36
@jdamore-linode jdamore-linode requested a review from a team as a code owner August 1, 2025 14:36
@jdamore-linode jdamore-linode requested review from coliu-akamai and dwiley-akamai and removed request for a team August 1, 2025 14:36
Copy link
Contributor

@coliu-akamai coliu-akamai left a comment

Choose a reason for hiding this comment

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

thanks @jdamore-linode!

@github-project-automation github-project-automation bot moved this from Review to Approved in Cloud Manager Aug 1, 2025
@linode-gh-bot
Copy link
Collaborator

Cloud Manager UI test results

🔺 3 failing tests on test run #4 ↗︎

❌ Failing✅ Passing↪️ Skipped🕐 Duration
3 Failing697 Passing5 Skipped143m 28s

Details

Failing Tests
SpecTest
linode-storage.spec.tsCloud Manager Cypress Tests→linode storage tab » delete disk
smoke-linode-landing-table.spec.tsCloud Manager Cypress Tests→linode landing checks » checks label and region sorting behavior for linode table
access-key.e2e.spec.tsCloud Manager Cypress Tests→object storage access key end-to-end tests » "before all" hook for "can create an access key with unlimited access - e2e"

Troubleshooting

Use this command to re-run the failing tests:

pnpm cy:run -s "cypress/e2e/core/linodes/linode-storage.spec.ts,cypress/e2e/core/linodes/smoke-linode-landing-table.spec.ts,cypress/e2e/core/objectStorage/access-key.e2e.spec.ts"

@jdamore-linode jdamore-linode merged commit 9f85345 into linode:develop Aug 1, 2025
34 of 35 checks passed
@github-project-automation github-project-automation bot moved this from Approved to Merged in Cloud Manager Aug 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

5 participants