cypress-crud-api-test
react-cypress-ts-vite-template
cypress-crud-api-test | react-cypress-ts-vite-template | |
---|---|---|
3 | 2 | |
8 | 2 | |
- | - | |
9.6 | 9.5 | |
3 days ago | 3 days ago | |
TypeScript | TypeScript | |
- | - |
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-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.
react-cypress-ts-vite-template
-
CI CD strategies for UI apps and deployed services
This YAML file details the CI implementation, including combined code coverage with CodeCov. For a simpler example without Cypress parallelization and code coverage, check the Github Actions YAML file of this template. The ideas presented here can be applied to any front-end application.
-
Improve Cypress e2e test latency by a factor of 20!!
This optimization will help speed up our test warmup time at scale, further simplify our plugin and task configurations. The process is described elaborately in this video, the PR, and the final code is shown in two simple template examples; CRA-repo, Vite-repo. This is the way we wish Cypress came out of the box.
What are some alternatives?
pizza-api
appsyncmasterclass-backend - Backend for a Twitter Clone built with Serverless Framework, JS, AWS AppSyc, Lambda, DynamoDB & Cognito.
cypress-data-session - Cypress command for flexible test data setup
cypress-esbuild-preprocessor - Bundle Cypress specs using esbuild
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
books - Self-learning exercises from my favorite JS related books
spok - Checks a given object against a given specification to keep you from writing boilerplate tests.
cy-spok - Playing with spok inside Cypress
github-action - GitHub Action for running Cypress end-to-end & component tests
cy-api - Cypress custom command "cy.api" for end-to-end API testing