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
We should setup CI for tests available into test projects, such as we're able to test AEs features via AEs themselves
We should at least cover Cypress ones since we already know how to setup them thanks to Milos, and we can link those to another project into Cypress Dashboard
Jest/Vitest tests should be simpler to setup than Cypress ones, but Jest AE doesn't seem to work with Vite right now
If possible, we should also run these tests when there's a release for app-webpack and app-vite minor (or patch?) version.
In these cases we should run only tests into the relevant test project: into test-project-vite if a new app-vite version is released and same for webpack. test-project-app won't have any new updates so it's not considered into this feature
The text was updated successfully, but these errors were encountered:
Replaces #2
We should setup CI for tests available into test projects, such as we're able to test AEs features via AEs themselves
We should at least cover Cypress ones since we already know how to setup them thanks to Milos, and we can link those to another project into Cypress Dashboard
Jest/Vitest tests should be simpler to setup than Cypress ones, but Jest AE doesn't seem to work with Vite right now
If possible, we should also run these tests when there's a release for app-webpack and app-vite minor (or patch?) version.
In these cases we should run only tests into the relevant test project: into test-project-vite if a new app-vite version is released and same for webpack. test-project-app won't have any new updates so it's not considered into this feature
The text was updated successfully, but these errors were encountered: