Gathering detailed insights and metrics for @quasar/quasar-app-extension-testing-unit-jest
Gathering detailed insights and metrics for @quasar/quasar-app-extension-testing-unit-jest
Installations
npm install @quasar/quasar-app-extension-testing-unit-jestReleases
65
@quasar/testing-unit-vitest v1.1.0
unit-vitest-v1.1.0
Published on 28 Aug 2024
@quasar/testing-e2e-jest v3.0.1
unit-jest-v3.0.1
Published on 10 Jul 2024
@quasar/testing-e2e-jest v3.0.0
unit-jest-v3.0.0
Published on 20 Jun 2024
@quasar/testing-e2e-cypress v6.1.0
e2e-cypress-v6.1.0
Published on 17 Apr 2024
@quasar/testing-unit-vitest v1.0.0
unit-vitest-v1.0.0
Published on 01 Mar 2024
@quasar/testing-e2e-cypress v6.0.0
e2e-cypress-v6.0.0
Published on 01 Mar 2024
Developer
Developer Guide
BETA
Module System
CommonJS
Min. Node Version
^14.15.0 || ^16.10.0 || >=18.0.0
Typescript Support
No
Node Version
NPM Version
Statistics
179 Stars
620 Commits
66 Forks
11 Watching
22 Branches
32 Contributors
Updated on 06 Nov 2024
Languages
TypeScript (47.13%)
JavaScript (26.95%)
Vue (22.81%)
HTML (2.03%)
SCSS (0.95%)
Sass (0.09%)
CSS (0.04%)
Total Downloads
Cumulative downloads
Total Downloads
2,278,556
Last day
-13.3%
1,802
Compared to previous day
Last week
-4.2%
8,132
Compared to previous week
Last month
-5.9%
35,017
Compared to previous month
Last year
-36.1%
426,746
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Versions
@quasar/testing
This is the monorepo for integrating the test-runner of your choice into your Quasar app.
You can install multiple pre-rigged testing harnesses (test runners) to your Quasar application, each one will:
- install the harness NPM package into your project;
- scaffold necessary configuration files;
- add script commands which expose some functionality of the respective harness.
App Extensions (such as these testing harnesses) only work with Quasar CLI, not with Vue CLI, nor by directly installing packages via a package manager as npm or yarn. Use
quasar ext add ...or the installation step won't be executed and configuration files won't be copied over.
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.
The Test Driven Design approach will help you to write better (and fewer) tests. Even though it may seem like it slows you down to some degree, this habit pays its dividends on the long term drastically reducing the number of public bugs and the project maintenance effort. Think of tests like insurance for your code that always pays out. On the other hand, not everything is worth being tested, or is worth being tested only at an higher level (eg. using an E2E tests instead of unit tests).
REMEMBER
Test the functionality, not the function
Table of contents
-
Provided App Extensions
-
Testing Harnesses Manager (DEPRECATED)
-
Unit testing
-
E2E testing
-
Quality Auditing (OUTDATED, not migrated to Qv2 yet)
-
Donations
The Quasar team spend a considerable amount of time studying, coding and maintaining App Extensions (AE) which save literally thousands of developers hours, days or weeks of work.
Does your business or personal projects depend on these App Extensions? How much time did we save you until now? Consider donating to help us maintain them and allow us to create new ones!
Installation
You can add test harnesses:
- in a centralized way via the Testing Harnesses Manager (DEPRECATED);
- using an "a-la-carte" approach, checking each harness documentation.
You can add multiple harnesses and even use them into your continuous integration pipelines.
Removal
You can remove a testing harness running:
1$ quasar ext remove @quasar/testing-unit-jest
This will remove the associated NPM package and run the Quasar App Extensions uninstall hook. If not done into the AE uninstall hook, the removal won't delete test or configuration files.
Reset
If you mess up your configuration and need to reset, or just want to check out if there has been any changes into new versions configuration, you should run:
1$ quasar ext add @quasar/testing-unit-jest
Be careful though, this will overwrite ALL existing files (including configurations) if you allow it to. Make sure to have some kind of version control in place before proceeding. This operation will also upgrade the NPM package and its dependencies.
To prevent installing new or updated dependencies, you should run:
1$ quasar ext invoke @quasar/testing-unit-jest
Upgrade
You can upgrade a testing harness and its dependencies by updating its related NPM package.
$ yarn add -D @quasar/quasar-app-extension-testing-unit-jest
This won't change existing test or configuration files.
Upgrade to a new major version with NPM
When upgrading between major versions, since there are major changes, we suggest you to remove and re-add the AE, to obtain lastest configuration files too.
Ensure your source control is clean before proceeding, then answer (y) and "Overwrite all" when prompted to overwrite existing files and individually git diff all changes manually to check out which changes you want to keep and which you want to revert.
1$ quasar ext remove @quasar/testing-unit-jest 2$ quasar ext add @quasar/testing-unit-jest
Testing Harnesses Manager (DEPRECATED)
Check out Testing Harnesses Manager AE documentation
Unit Testing
Jest
Check out Jest AE documentation
Vitest
Check out Vitest AE documentation
E2E Testing
We recommend testing webapps with Cypress if you target Chrome-based browsers (Chrome, Edge, Electron) or Firefox - but if you want to test Safari or Cordova/Capacitor apps, then you should consider using webdriver.io.
Cypress
Check out Cypress AE documentation
Quality Auditing (OUTDATED, not migrated to Qv2 yet)
1$ 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.
Further Reading
Books
- Testing Vue.js Applications by Edd Yerburgh, the author of the
@vue/test-utilsrepo - Free Vue Testing Handbook
Tutorials
- Introduction to TDD
- Overview of JavaScript testing 2020
- Unit Testing Vue Router with Jest
- Jest tests debugging
Documentation
Contributing
Contributions to this repository are highly desirable, see the Contribution Guidelines for more details. Please note: project coordination takes place on the Discord server.
Contributors
- ilcallo
- nothingismagick
- nklayman
- Allan Gaunt
- andreiTn
- fansanelli
- mgibson91
- eugene
- bloo_df
- PhearZero
License
MIT ©2022 - present - Paolo Caleffi & Razvan Stoenescu
All Icons © the respective owners
No vulnerabilities found.
Reason
7 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
Reason
no binaries found in the repo
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
Found 3/23 approved changesets -- score normalized to 1
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 10 are checked with a SAST tool
Reason
50 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-67hx-6x53-jw92
- Warn: Project is vulnerable to: GHSA-wf5p-g6vw-rhxx
- Warn: Project is vulnerable to: GHSA-8hc4-vh64-cxmj
- Warn: Project is vulnerable to: GHSA-qwcr-r2fm-qrc7
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-pxg6-pf52-xh8x
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-rv95-896h-c2vc
- Warn: Project is vulnerable to: GHSA-qw6h-vgh9-j6wx
- Warn: Project is vulnerable to: GHSA-jchw-25xp-jwwc
- Warn: Project is vulnerable to: GHSA-cxjh-pqwp-8mfp
- Warn: Project is vulnerable to: GHSA-pfq8-rq6v-vf5m
- Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
- Warn: Project is vulnerable to: GHSA-9wv6-86v2-598j
- Warn: Project is vulnerable to: GHSA-7fh5-64p2-3v2j
- Warn: Project is vulnerable to: GHSA-gcx4-mw62-g8wm
- Warn: Project is vulnerable to: GHSA-m6fv-jmcg-4jfg
- Warn: Project is vulnerable to: GHSA-cm22-4g7w-348p
- Warn: Project is vulnerable to: GHSA-c24v-8rfc-w8vw
- Warn: Project is vulnerable to: GHSA-8jhw-289h-jh2g
- Warn: Project is vulnerable to: GHSA-4vvj-4cpr-p986 / GHSA-64vr-g452-qvp3
- Warn: Project is vulnerable to: GHSA-9cwx-2883-4wfx
- Warn: Project is vulnerable to: GHSA-96g7-g7g9-jxw8
- Warn: Project is vulnerable to: GHSA-c7qv-q95q-8v27
- Warn: Project is vulnerable to: GHSA-wr3j-pwj9-hqq6
- Warn: Project is vulnerable to: GHSA-3h5v-q93c-6h6q
- Warn: Project is vulnerable to: GHSA-p8p7-x288-28g6
- Warn: Project is vulnerable to: GHSA-g3ch-rx76-35fx
- Warn: Project is vulnerable to: GHSA-gp2j-mg4w-2rh5
- Warn: Project is vulnerable to: GHSA-pfrx-2q88-qq97
- Warn: Project is vulnerable to: GHSA-w7q9-p3jq-fmhm
- Warn: Project is vulnerable to: GHSA-xvf7-4v9q-58w6
- Warn: Project is vulnerable to: GHSA-p6mc-m468-83gw
- Warn: Project is vulnerable to: GHSA-35jh-r3h4-6jhm
- Warn: Project is vulnerable to: GHSA-vh95-rmgr-6w4m / GHSA-xvch-5gv4-984h
- Warn: Project is vulnerable to: GHSA-5rrq-pxf6-6jx5
- Warn: Project is vulnerable to: GHSA-8fr3-hfg3-gpgp
- Warn: Project is vulnerable to: GHSA-gf8q-jrpm-jvxq
- Warn: Project is vulnerable to: GHSA-2r2c-g63r-vccr
- Warn: Project is vulnerable to: GHSA-cfm4-qjh2-4765
- Warn: Project is vulnerable to: GHSA-x4jg-mjrx-434g
- Warn: Project is vulnerable to: GHSA-3j8f-xvm3-ffx4
- Warn: Project is vulnerable to: GHSA-j9fq-vwqv-2fm2
- Warn: Project is vulnerable to: GHSA-pqw5-jmp5-px4v
- Warn: Project is vulnerable to: GHSA-f5x3-32g6-xq36
- Warn: Project is vulnerable to: GHSA-72xf-g2v4-qvf3
- Warn: Project is vulnerable to: GHSA-h6q6-9hqw-rwfv
- Warn: Project is vulnerable to: GHSA-5fg8-2547-mr8q
- Warn: Project is vulnerable to: GHSA-crh6-fp67-6883
- Warn: Project is vulnerable to: GHSA-p9pc-299p-vxgp
Score
3.6
/10
Last Scanned on 2024-11-18
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More