This is the monorepo for integrating the test-runner of your choice into your Quasar-Framework app v1.0 and above.


High level overview

You can install multiple pre-rigged testing harnesses to your existent 1.0+ Quasar application by running a simple command. This command will pull and install a node module (with dependencies) into your project’s package.json, place necessary configuration files as appropriate and if you so choose, it will also add script commands that expose some of the functionality of the respective harness. You can add multiple harnesses and even use them for your continuous integration pipelines - as appropriate.

Testing is not in and of itself hard. The most complicated part is setting up the testing harness. The trick lies in knowing what to test. If you are new to testing, it is absolutely imperative that you familiarize yourself with some of the concepts and patterns. There are some links for further reading at the end of this document page.

Test the functionality, not the function


$ cd your-quasar-project
$ quasar ext add @quasar/testing

The lightweight extension installer will ask you which testing harnesses you want to install. Then it will install the respective extensions for these harnesses, which you can configure as you like. It is how multiple testing harnesses are ideally managed within a Quasar project.

It will provide you with a new quasar run command that you can use to execute test-runners - and even your HMR dev environment at the same time. This approach can, for example, be quite helpful if you need to pass quasar.ctx to the test runner…

# Example to run jest --watch && dev server
$ quasar run @quasar/testing test --unit=jest.watch.coverage --dev=pwa

If you ever need to review your choices you can take a look at quasar.extensions.json.

If you don’t want to install the base package, you don’t have to do so. You can install each test harness app extension individually. They are completely standalone.

Updating / Resetting

If you mess up your configuration and need to reset - or just want the latest Quasar-approved packages, this would be the way to do it:

$ quasar ext add @quasar/testing-unit-jest

Be careful though, reinstalling will overwrite ALL existing files (including configurations) if you tell it to. Also, it will install the new packages (if there are any). To prevent installing new or updated node modules, you may do this:

$ quasar ext add @quasar/testing-e2e-cypress --skip-pkg


If you want to remove the testing harness, you can run:

$ quasar ext --remove @quasar/testing-unit-jest

This will remove the associated node module and its dependencies, but it will not delete or modify any files.


Unit Testing

We recommend using Jest 24. There are many, many reasons for this. Just take our word for it.

$ quasar ext add @quasar/testing-unit-jest

We have included:

::: warning If you are not using git or mercurial to manage your code, jest –watch will not work because jest uses version-control to track which files can be looked at. This leaves you with two options:

  1. run git init in your project directory (or permit the installer to do it for you)
  2. use the alternative --watchAll flag for Jest - which will probably have a performance hit - make sure you are ignoring all the folders possible in your Jest configuration. :::

We have included the optional ability to place your test code inside your vue files, should you choose to do so. It will be rendered by webpack HMR, and there is a script we have included that will run both the quasar dev command and jest --watch

<test lang="jest">
  /* your complete test file here */

::: tip You may notice that your IDE doesn’t know how to parse the test block, so go into the <test/> block, press <alt> + <enter>, select ‘inject language or reference’ and select javascript. This will grant <test/> blocks autocomplete. :::

e2e Testing

We recommend testing webapps with Cypress - but if you are building for multiple platforms (electron, cordova and web), then its a good idea to use webdriver.io.


$ quasar ext add @quasar/testing-e2e-cypress

::: warning You must have a running dev server in order to run integration tests. Be sure to either set the "baseUrl" in the /cypress.json file or use the test command provided by the base @quasar/testing extension. :::

We actually recommend installing Cypress globally, because otherwise it is a pretty large package to weigh down the already heaviest thing in the universe


$ quasar ext add @quasar/testing-e2e-wdio
$ yarn selenium:install && selenium:start

WIP - please help battle test this harness.

Prior Work: https://github.com/fansanelli/quasar-webdriver/blob https://github.com/NodeJunkie/quasar-webdriver/tree/feat/BackportToQuasar%231

Quality Auditing

$ quasar ext add @quasar/testing-quality

Auditing the quality of your app is something you want to do before you go in production. Depending on your perspective, quality can mean many things. So we have put together a few tools that we think can help you have a qualitatively better project.

The Lighthouse tool can help you identify issues with your PWA app, but only if you serve the built version of your project. If you use it a lot, consider installing it globally.

Snyk is a tool for identifying node modules that have security implications. Running this regularly will keep you alerted to issues that may be stemming from repositories you use.

Node License Finder (nlf) is a free tool you can use to catalog all the licenses of the hundreds of open-source projects you are using in your project.

Where is %_my_darling_% harness?

There will be more and more test-harnesses coming as time permits. If you would like to help us add official harnesses, please get in touch on Discord. Do not merely make a PR, as there are several people working in private forks and it is likely that the harness you are interested in may already be in some stage of development.


The packages in this repo are designed to be installed only by the Quasar framework. They follow the following naming convention:

Because of the way that Quasar internally maps extensions (pruning “app-extension-“), the ava test-runner would be @quasar/test-unit-ava.

Although you could probably install them all with yarn, it is highly recommended to follow the normal approach of using the quasar CLI because of the template files copied over. Furthermore, this will only work with the CLI for Quasar 1.0, not with vue-cli. If you are interested in breaking the warranty, if you were only interested in integrating the node_module dependencies from ava and spectron into your app, technically you could merely run:

$ yarn add @quasar/test-testing 
$ yarn add @quasar/test-unit-ava
$ yarn add @quasar/test-e2e-cypress

The test-driven-design approach will also help you to write better (and fewer) tests. Even though it may seem like it slows you down to some degree, this habit of great programmers pays its dividends when other developers accidentally change the interface. Think of tests like insurance for your code that always pays out.


Clone this repository and run yarn init.

Then create a 1.0 Quasar app. Go into the package.json and add this line:

    "@quasar/quasar-app-extension-testing-unit-jest": "link:../%path_to_quasar-testing%/packages/unit-%_your-harness_%",

Then run yarn and finally:

$ quasar ext add @quasar/testing-unit-%_your-harness_% --skip-pkg

Please consult the forthcoming documentation about how to create app extensions at the main Quasar docs - or learn by copying.

Integration Roadmap

Test harnesses currently verified to have valid “integration” are checked off in the following list:





Further Reading





Contributions to this repository are highly desirable. Before you make a PR, please open an issue, create a fork and PR. See the Contribution Guidelines for more details. Please note: Project coordination takes place on the Discord server.


Special Thanks

Denjell would like to give a special shout out to all of the people who helped test the testing framework during the transition from 0.17 to 1.0



MIT ©2018 - present - D.C. Thompson & Razvan Stoenescu

All Icons © the respective owners