You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently our Cypress test suite is running on Github CI and take around 30 minutes to finish. Those are currently running on all branches and on each commit. Also tests are failing randomly because the headless browser is not finding specific elements which should be there after the grace time of 10s.
Open Tasks
Adjust Github CI
Only run on main and release-* branches
Only run on PRs when a PR was approved
Refactor tests to run more performant
Fix performance issues in combination with Github CI and the headless browser
Other notes
We also thought about adding unit tests specifically for the core and ui library packages to test helper and core functions and classes which could run more frequently.
Testing specific frameworks would also be a nice addition as a test on release-* branches so we can test if Tiptap is correctly installed in various setups.
Those could include
Next.js
CRA
Vite
Nuxt
Vanilla Webpack
This could avoid future issues with broken builds with said frameworks.
The text was updated successfully, but these errors were encountered:
What’s the bug you are facing?
Currently our Cypress test suite is running on Github CI and take around 30 minutes to finish. Those are currently running on all branches and on each commit. Also tests are failing randomly because the headless browser is not finding specific elements which should be there after the grace time of 10s.
Open Tasks
main
andrelease-*
branchesOther notes
We also thought about adding unit tests specifically for the core and ui library packages to test helper and core functions and classes which could run more frequently.
Testing specific frameworks would also be a nice addition as a test on
release-*
branches so we can test if Tiptap is correctly installed in various setups.Those could include
This could avoid future issues with broken builds with said frameworks.
The text was updated successfully, but these errors were encountered: