Quasar testing AE aren't maintained and are incompatible with latest Quasar versions

[FelixNumworks]

Description

In the official Quasar documentation about testing and auditing, the Quasar testing AE are presented as the official solution to test our Quasar app. This is what we use in my project.

But if you go on the Quasar Testing repo, you can see that it has received no updates since November 2025, and even before that, the updates have been very sparse since May 2025.

You can see there that:

• The unit-vitest AE is incompatible with @quasar/app-vite@2.4+
• The unit-vitest AE doesn't support vitest@4+
• The e2e-cypress AE is incompatible with @quasar/app-vite@2.4+
• The e2e-cypress AE doesn't support cypress@15+

Is this solution still maintained ? Is it still the official recommandation ?
If not, the docs should be updated. But ideally, I'd like someone to help me fix the descrepencies I presented above :(

Documentation Section URL

https://github.com/quasarframework/quasar/blob/5e65cbeb72b65b276dc277781141be36ad5afeae/docs/src/pages/quasar-cli-vite/testing-and-auditing.md

Flavour

Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)

Areas

Quasar CLI Commands/Configuration (@quasar/cli | @quasar/app-webpack | @quasar/app-vite)

[FelixNumworks]

@yusufkandemir I'm not sure just assigning @IlCallo will help here, as they are already aware of the issues on the other repo. Maybe they just don't have the time to handle this.

That's why I reached to you here on the main repo in the first place. To see if someone else might be able to help.

[yusufkandemir]

@FelixNumworks do not worry. I know him, I am in touch with him, and I am assigning him for a reason. He has been planning to work on it for some time, but we were busy. He can provide a status update, estimate, etc.

[FelixNumworks]

Ok thanks a lot 🙏

[IlCallo]

Hey there, and first of all: sorry for the long silence on my side

As you correctly stated, we started updating testing AEs in the last quarter of last year, after a Quasar update caused testing AEs to be incompatible with v2.4 onwards
That's on us, since it was caused by a lack of communication within Quasar team

I still managed to make everything work around November, but I postponed the release as I was waiting for some changes within Quasar core, which would make the release more stable (even if those changes weren't really blocking)

Unfortunately, from December to March my company underwent big and mostly unforseen organizational changes, which basically absorbed all my time
I did notice your comments and PRs on the testing repo, but I was putting off so many fires at once that I didn't even had the time to properly read them

In a couple weeks I should be done with this really stressful period, which means I should be able to get back on the releases I had prepared back in November and wrap them up
I've been planning to do so for the past 3-4 weeks actually (which is why Yusuf mentioned that), but more unforseen urgencies forced me to postpone it week after week

After I complete these releases, I probably won't be able to spend much time on open source contributions (and that really saddens me), as my role within the company changed and I'll be required elsewhere
If anyone is willing to maintain testing AEs, I'll gladly help onboarding someone else as maintainer and guide them

[FelixNumworks]

Thanks a lot for your response. I appreciate the update.
No worries at all, I understand that your situation is complicated. I mainly wanted to check whether the project was still actively maintained or not.

If anyone is willing to maintain testing AEs, I'll gladly help onboarding someone else as maintainer and guide them

Unfortunately, my company is quite small and I wouldn’t be able to take on a maintainer role for an external project.
That said, I'm able to contribute with occasional PRs when I can.