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: Use nanoid instead of UUID in e2e tests for wf names (no-changelog) #9717

Merged

Conversation

tomi
Copy link
Contributor

@tomi tomi commented Jun 12, 2024

Summary

Contains 2 changes to e2e test:

  • test: Enable running only single suite with test:e2e:all script. E.g. pnpm test:e2e:all 1-workflows.cy
  • test: Use nanoid instead of uuid when generating a random workflow name

We have been adding a random uuid to workflow names in some e2e tests.
Cypress is actually pretty slow in typing text to input fields. Since
uuid is 36 characters, this adds some delay to our e2e tests. This
change shaves some seconds off by using a 12 character long
nanoid instead.

On my local machine 19-execution suite execution time went from 47.3s
to 42.7s (3 test run avg). 1-workflows went from 27.3s to 24.7s.

Review / Merge checklist

  • PR title and summary are descriptive. (conventions)
  • Docs updated or follow-up ticket created.
  • Tests included.
  • PR Labeled with release/backport (if the PR is an urgent fix that needs to be backported)

tomi added 2 commits June 12, 2024 15:40
We have been adding a random uuid to workflow names in some e2e tests.
Cypress is actually pretty slow in typing text to input fields. Since
uuid is 36 characters, this adds some delay to our e2e tests. This
change shaves some seconds off by using a 12 character long
nanoid instead.

On my local machine 19-execution suite execution time went from 47.3s
to 42.7s (3 test run avg). 1-workflows went from 27.3s to 24.7s.
@n8n-assistant n8n-assistant bot added the n8n team Authored by the n8n team label Jun 12, 2024
cypress/support/commands.ts Outdated Show resolved Hide resolved
@tomi tomi requested a review from netroy June 12, 2024 14:22
Copy link
Member

@netroy netroy left a comment

Choose a reason for hiding this comment

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

🎉

Copy link

cypress bot commented Jun 12, 2024

5 flaky tests on run #5454 ↗︎

0 388 0 0 Flakiness 5

Details:

🌳 🖥️ browsers:node18.12.0-chrome107 🤖 tomi 🗃️ e2e/*
Project: n8n Commit: 0f9caf5ca2
Status: Passed Duration: 04:46 💡
Started: Jun 12, 2024 4:26 PM Ended: Jun 12, 2024 4:30 PM
Flakiness  5-ndv.cy.ts • 2 flaky tests

View Output Video

Test Artifacts
NDV > should not retrieve remote options when required params throw errors Screenshots Video
NDV > Stop listening for trigger event from NDV Screenshots Video
Flakiness  10-undo-redo.cy.ts • 2 flaky tests

View Output Video

Test Artifacts
Undo/Redo > should undo/redo adding nodes Test Replay Screenshots Video
Undo/Redo > should undo/redo adding connected nodes Test Replay Screenshots Video
Flakiness  24-ndv-paired-item.cy.ts • 1 flaky test

View Output Video

Test Artifacts
NDV > resolves expression with default item when input node is not parent, while still pairing items Test Replay Screenshots Video

Review all test suite changes for PR #9717 ↗︎

Copy link
Contributor

✅ All Cypress E2E specs passed

@tomi tomi merged commit 58f00bb into master Jun 13, 2024
26 checks passed
@tomi tomi deleted the test-use-nanoid-instead-of-uuid-in-e2e-tests-for-wf-names branch June 13, 2024 06:39
adrian-martinez-onestic pushed a commit to onesdata/n8n-fork that referenced this pull request Jun 20, 2024
adrian-martinez-onestic pushed a commit to onesdata/n8n-fork that referenced this pull request Jun 20, 2024
@janober
Copy link
Member

janober commented Jun 20, 2024

Got released with [email protected]

1 similar comment
@janober
Copy link
Member

janober commented Jun 20, 2024

Got released with [email protected]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
n8n team Authored by the n8n team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants