quasar-testing
quasar-testing copied to clipboard
quasarframework
Testing Harness App Extensions for the Quasar Framework 2.0+
We need to keep test-projects up to date with the changes we do into AE templates This could be done by running a sync for all projects and all AEs,...
With Cypress moving into component testing domain, and Jest overlapping that domain too, we should probably rename AEs to avoid the "test type" bit, as it doesn't really make sense...
Since Qv2 it's possible to use TS for Quasar AE API files This requires some changes both to the AE structure/compilation process, some file names and package.json fields must be...
It came out many times lately, especially since they jumped into component testing hype train I don't feel it's a priority, but if anyone wants to take responsability for this...
I think [this AE](https://github.com/quasarframework/quasar-testing/tree/dev/packages/quality) idea was cool, but there has not been enough bandwidth to work on it so it fell behind I also have no idea how it works,...
Vite 3.0 will probably be released around autumn/winter, judging by their public milestone on GH We should prepare for the upgrade, AFAIK Vite 3 will have quite some breaking changes...
After we release Vitest AE, we should add some smoke tests for it as we do for Jest and Cypress We should use the same we use for Jest, since...
It isn't working with Vite CLI for some reason, I think it worked in the past right after the Vite CLI release, but I wouldn't bet on it We cannot...
After we release at least a beta version of [Jest AE v3](https://github.com/quasarframework/quasar-testing/issues/241), we can switch docs into testing.quasar.dev with Qv2 ones
Jest AE v3 is still in alpha and have many problems It's generally less suited for component testing when compared to Cypress or Playwright, but many people keep using it...
Metadata
Owner
Metadata
Testing Harness App Extensions for the Quasar Framework 2.0+