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

feat: add burn-in to test execution logic #27965

Closed

Conversation

MuazOthman
Copy link
Contributor

  • Closes CYCLOUD-1665

Additional details

Steps to test

How has the user experience changed?

PR Tasks

@MuazOthman MuazOthman changed the title Initial work to add burn-in to test execution logic CYCLOUD-1665 feat: add burn-in to test execution logic Oct 3, 2023
@cypress
Copy link

cypress bot commented Oct 3, 2023

19 failed tests on run #51421 ↗︎

19 9719 462 0 Flakiness 0

Details:

Initial work to add burn-in to test execution logic
Project: cypress Commit: 265b8271c4
Status: Failed Duration: 15:45 💡
Started: Oct 3, 2023 9:48 PM Ended: Oct 3, 2023 10:03 PM
Failed  commands/assertions.cy.js • 0 failed tests • 5x-driver-electron

View Output Video

Test Artifacts
Failed  commands/actions/check.cy.js • 0 failed tests • 5x-driver-electron

View Output Video

Test Artifacts
Failed  e2e/origin/origin.cy.ts • 0 failed tests • 5x-driver-electron

View Output Video

Test Artifacts
Failed  commands/actions/type_events.cy.js • 0 failed tests • 5x-driver-electron

View Output Video

Test Artifacts
Failed  e2e/origin/validation.cy.ts • 0 failed tests • 5x-driver-electron

View Output Video

Test Artifacts

The first 5 failed specs are shown, see all 987 specs in Cypress Cloud.

Review all test suite changes for PR #27965 ↗︎

// If there is AT LEAST one failed test attempt, we know we need to apply retry logic.
// Otherwise, the test might be burning in (not implemented yet) OR the test passed on the first attempt,
// meaning retry logic does NOT need to be applied.
if (failedTests.length > 0) {
test.nextAttemptStrategy = 'RETRY'
Copy link
Contributor

Choose a reason for hiding this comment

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

nextAttemptStrategy is only referenced to set thisAttemptStrategy; is this logic necessary?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is so we can indicate if the next attempt is to be made as part of a retry. I'm not sure if there's another way to do it.

outerTestStatus = 'passed'
test.final = true
shouldAttemptsContinue = false
test.reasonToStop = 'PASSED_MET_THRESHOLD'
Copy link
Contributor

Choose a reason for hiding this comment

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

reasonToStop is only set, and never referenced - is this a field we'll be sending to the cloud?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, see the description here

@MuazOthman MuazOthman closed this Nov 7, 2023
@MuazOthman MuazOthman deleted the muaz/support-burn-in-attempts branch January 4, 2024 16:42
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

Successfully merging this pull request may close these issues.

2 participants