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

test: [M3-6608] - Add Linode power off, power on and reboot tests #9980

Merged
merged 2 commits into from
Jan 2, 2024

Conversation

cliu-akamai
Copy link
Contributor

Description 📝

Add regression tests for powering on/off and rebooting Linodes

Major Changes 🔄

  • Add regression tests to power on/off and reboot Linodes

How to test 🧪

yarn cy:run -s "cypress/e2e/core/linodes/switch-linode-state.spec.ts"

@cliu-akamai cliu-akamai requested a review from a team as a code owner December 7, 2023 22:05
@cliu-akamai cliu-akamai requested review from jdamore-linode and removed request for a team December 7, 2023 22:05
@cliu-akamai cliu-akamai requested a review from a team as a code owner December 7, 2023 22:07
@cliu-akamai cliu-akamai requested review from carrillo-erik and tyler-akamai and removed request for a team December 7, 2023 22:07
Copy link

github-actions bot commented Dec 7, 2023

Coverage Report:
Base Coverage: 86.51%
Current Coverage: 86.51%

@@ -0,0 +1,5 @@
---
"@linode/manager": Added
Copy link
Contributor

Choose a reason for hiding this comment

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

I had a similar PR where I only added new tests and was unsure of which identifier to use for the changeset. In my case I ended up going with Tests. My decision was based on the descriptions found under the Commit Types in the Pull Request Template:

test: New tests or changes to existing tests. Does not change the production code.

Copy link
Contributor

Choose a reason for hiding this comment

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

+1 to using tests for the changeset category

@carrillo-erik
Copy link
Contributor

Looks good. I ran the tests locally and verified that they all passed ✅ ✅ ✅

Screenshot

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.

confirmed all specs passed - thanks Cassie!

@@ -0,0 +1,5 @@
---
"@linode/manager": Added
Copy link
Contributor

Choose a reason for hiding this comment

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

+1 to using tests for the changeset category

.should('be.visible')
.within(() => {
containsVisible('Shutting Down');
cy.contains('Offline', { timeout: 300000 }).should('be.visible');
Copy link
Contributor

Choose a reason for hiding this comment

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

is 5 minutes too long? Not sure what our standards are.

@tyler-akamai
Copy link
Contributor

LGTM, nice clean tests. I dont have baker access, but not sure whats causing the failure.
Screenshot 2023-12-17 at 3 12 36 PM

@coliu-akamai coliu-akamai added Testing Approved Multiple approvals and ready to merge! labels Dec 20, 2023
@cliu-akamai cliu-akamai merged commit b91455f into linode:develop Jan 2, 2024
14 of 15 checks passed
@cliu-akamai cliu-akamai deleted the feature/M3-6608 branch January 2, 2024 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Approved Multiple approvals and ready to merge! Testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants