cypress-skip-test
cypress-crud-api-test
cypress-skip-test | cypress-crud-api-test | |
---|---|---|
2 | 3 | |
176 | 8 | |
- | - | |
0.8 | 9.6 | |
over 1 year ago | 7 days ago | |
JavaScript | TypeScript | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cypress-skip-test
-
Effective Test Strategies for Deployed NodeJS Services using LaunchDarkly Feature Flags and Cypress. Part2: testing
We can take advantage of another one of Gleb's fantastic plugins cypress-skip-test. npm install -D @cypress/skip-test and Add the below line to cypress/support/index.js:
-
The 32+ ways of selective testing with Cypress: a unified, concise approach to selective testing in CI and local machines
cypress-skip-test - this is a special one for ability to negate tests and have combinations in itself
cypress-crud-api-test
-
Improve Cypress e2e test latency by a factor of 20!!
Any blog post is lackluster without working code, so here is a PR from scratch adding esbuild to a repository with Cypress. You can find the final code on the main branch of the repository we will use in this example. Other examples can be found at tour-of-heroes-react-cypress-ts as well as a VueJS app. The framework and the bundler the framework uses are irrelevant, any repo can take advantage of cypress-esbuild-preprocessor for e2e tests.
-
Effective Test Strategies for Deployed NodeJS Services using LaunchDarkly Feature Flags and Cypress. Part2: testing
This is part two of a multi-part series. In the previous post we setup the flags, now we will test them. Before diving into testing feature flags, we will setup Cypress and transfer over the final CRUD e2e spec from the repo cypress-crud-api-test. That repo was featured in the blog post CRUD API testing a deployed service with Cypress. Note that the said repo and this service used to be separated - that is a known anti-pattern - and now we are combining the two in a whole. The change will provide us with the ability to use the LaunchDarkly (LD) client instance to make flag value assertions. We would not have that capability if the test code was in a separate repo than the source code, unless the common code was moved to a package & was imported to the two repos. In the real world if we had to apply that as a solution, we would want to have valuable trade-offs.
-
CRUD API testing a deployed service with Cypress using cy-api, spok, cypress-data-session & cypress-each
The code for this entire guide is available at GitHub. For learning purposes, you can check out the branch base to start from scratch and follow the guide. main has the final version of the repo. The code samples are setup to copy paste into the repo and work at every step.
What are some alternatives?
cypress-fail-fast - A Cypress plugin to skip tests on first failure.
pizza-api
github-action - GitHub Action for running Cypress end-to-end & component tests
cypress-data-session - Cypress command for flexible test data setup
cypress-react-app-actions - Access the internals of React components from Cypress end-to-end tests
cypress-ld-control - Set LaunchDarkly feature flags from Cypress tests
react-hooks-in-action-with-cypress - React Hooks in Action Book, with Cypress e2e & component tests
angular-playground - angular, cypress, jest, spectator, combined code coverage, pwa, aws s3, circleci, gitlab
books - Self-learning exercises from my favorite JS related books
cypress-grep - Filter tests using substring
spok - Checks a given object against a given specification to keep you from writing boilerplate tests.