@clerk/testing
Advanced tools
Utilities to help you create E2E test suites for apps using Clerk
This package provides utilities for testing Clerk applications.
It currently supports the following testing frameworks:
>=18.17.0 or laternpm install @clerk/testing --save-dev
Learn how to use @clerk/testing with different frameworks:
You can get in touch with us in any of the following ways:
We're open to all community contributions! If you'd like to contribute in any way, please read our contribution guidelines and code of conduct.
@clerk/testing follows good practices of security, but 100% security cannot be assured.
@clerk/testing is provided "as is" without any warranty. Use at your own risk.
For more information and to report security issues, please refer to our security documentation.
This project is licensed under the MIT license.
See LICENSE for more information.
FAQs
Utilities to help you create E2E test suites for apps using Clerk
The npm package @clerk/testing receives a total of 33,642 weekly downloads. As such, @clerk/testing popularity was classified as popular.
We found that @clerk/testing demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 8 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Opengrep continues building momentum with the alpha release of its Playground tool, demonstrating the project's rapid evolution just two months after its initial launch.
Security News
FSF files an amicus brief against Neo4j, defending the AGPL and warning against adding restrictive terms that undermine free software rights.
Research
Security News
Malicious PyPI package ‘set-utils’ steals Ethereum private keys by exfiltrating them through blockchain transactions via the Polygon RPC.