-
Notifications
You must be signed in to change notification settings - Fork 7.8k
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(editor): Update copy: Execute
--> Test
#8137
Conversation
Execute
--> Test
Execute
--> Test
Execute
--> Test
(no-changelog)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
2 flaky tests on run #3617 ↗︎
Details:
17-sharing.cy.ts • 1 flaky test
29-templates.cy.ts • 1 flaky test
Review all test suite changes for PR #8137 ↗︎ |
✅ All Cypress E2E specs passed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
@@ -42,7 +42,7 @@ | |||
{ | |||
"parameters": {}, | |||
"id": "551313bb-1e01-4133-9956-e6f09968f2ce", | |||
"name": "When clicking \"Execute Workflow\"", | |||
"name": "When clicking \"Test Workflow\"", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why did you need to update the fixtures? the tests should have worked even with the old node names, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
they kept breaking because we were using some of then to assert the exact label, so updated it all of them
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why did they keep breaking? the node names of imported workflows should not change, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Existing display names will not change! I only change it there because for some tests we were using this fixtures and asserting that the node display name was "Execute Node" instead "Test Node" so I changed it on all fixtures to avoid issues. I can revert the changes, and run the e2e tests again and only rename in the fixtures where we assert the new name.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah I see.. new nodes added in tests would need to be updated.. but not imported fixtures in tests.. it's your call here.. it's fine either way
Execute
--> Test
(no-changelog)Execute
--> Test
|
|
✅ All Cypress E2E specs passed |
Got released with |
Summary
Title self explanatory
Related tickets and issues
https://linear.app/n8n/issue/ADO-129/update-copy-execute-test
Review / Merge checklist
(no-changelog)
otherwise. (conventions)