Monorepo with Qase TestOps reporters for JavaScript testing frameworks.
For all of our reporters, there are two versions:
If you're just starting, pick v2. If your project is using a v1 reporter, check out the reporter's readme for the migration guide.
| Name | Package name | v2 series | v1 series |
|---|---|---|---|
| Qase JavaScript Reporters | |||
| CucumberJS | cucumberjs-qase-reporter |
✅ released | 🗿deprecated |
| Cypress | cypress-qase-reporter |
✅ released | 🗿deprecated |
| Jest | jest-qase-reporter |
✅ released | 🗿deprecated |
| Newman | newman-reporter-qase |
✅ released | 🗿deprecated |
| Playwright | playwright-qase-reporter |
✅ released | 🗿deprecated |
| Testcafe | testcafe-reporter-qase |
✅ released | 🗿deprecated |
| Mocha | mocha-qase-reporter |
not available | 🧪 open beta |
| WebDriverIO | wdio-qase-reporter |
not available | 🧪 open beta |
| Qase JavaScript SDK | |||
| Common functions library | qase-javascript-commons |
✅ released | not available |
| JavaScript API client | qaseio |
✅ released | 🗿deprecated |
What each status means:
The "✅ released" reporters are stable and well-tested versions. They will receive more new features as well as bugfixes, should we find bugs.
The "🧪 open beta" reporters are in active development and rigorous testing. It's completely usable (and much more fun to use than v1), but there can be some bugs and minor syntax changes. When starting a new test project, the "🧪 open beta" versions are the recommended choice. For existing projects, we recommend planning a migration — see the migration section in each reporter's readme and try out the new features.
The "🧰 closed beta" reporters are in active development, and can still have major bugs and future syntax changes. However, we encourage experimenting with them. Your feedback is always welcome.
The v1 series reporters in the "🗿stable" or "🗿deprecated" status only get some fixes, but no new features.