tour-of-heroes-react-cypress-ts
Cypress
tour-of-heroes-react-cypress-ts | Cypress | |
---|---|---|
6 | 174 | |
22 | 46,226 | |
- | 0.5% | |
9.4 | 9.8 | |
8 days ago | 6 days ago | |
TypeScript | JavaScript | |
- | 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.
tour-of-heroes-react-cypress-ts
-
Cypress Component Testing vs React Test Library - the complete comparison
ToH is the final app built in the book CCTDD: Cypress Component Test Driven Design. It has a few dozen Cypress component tests and their RTL mirrors. We will cover a few examples to showcase the main differences.
-
CI CD strategies for UI apps and deployed services
We'll start by examining a Tour of Heroes repo, featured in the book CCTDD: Cypress Component Test Driven Design. This repository demonstrates various test checks, including lint (ESLint), type checks (TS), unit tests (Jest), and Cypress component tests & end-to-end tests. The tests are parallelized to reduce feedback time to approximately five minutes, which is an optimal duration to promote a continuous feedback loop for this size of repo.
-
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.
-
Ramda & Functional Programming with React & TypeScript
This is a new section in my book, chapter 20 of CCTDD: Cypress Component Test Driven Design. It is being shared here to reach a wider audiance. All the content is paired with the application Tour of Heroes in React Cypress TS. The PR for the functional refactor can be found in here. While all the code is copy pastable, you can find working prototypes here and here.
-
Triple combined coverage with Typescript
In the previous post we covered triple combined coverage in a React app written in JS . Alas, Typescript can be tricky with combined code coverage. We continue the series with a Typescript example using the React TS app featured in the book CCTDD: Cypress Component Test Driven Design. The application built in the book is in TS, includes Cypress e2e, CT tests, as well as React Testing Library mirrors of them. The repo tour-of-heroes-react-cypress-ts has the final version of the repo with triple combined coverage setup. The state of the repo prior to code coverage is in the branch before-code-coverage and there is a sample PR for reproducing this guide.
Cypress
-
Simulating Internet Outage and Recovery using Cypress
In this blog post, we'll explore a Cypress test that replicates this scenario, utilizing the powerful intercept command to manipulate network requests and responses.
-
Testing Defer Blocks in Angular with Cypress
Recently I came across this issue while triaging some issues at Cypress. (Shout out to MattiaMalandrone for creating an issue with clear instructions for how to reproduce). After quickly replicating the issue I sought after a solution which ultimately inspired me to write this article.
- Cypress changed older versions to block third-party plugins (ignoring lockfiles)
- Cypress can't open Tesla.com website
-
What is Playwright?
While similar to Puppeteer, Cypress, and Selenium, there are some differences. Let’s find out what they are.
- Episode 23/37: ISR in Angular, Cypress & Playwright
-
/Does Cypress Component Testing Work With Libraries
This questions was asked a while ago and pretty much went unanswered: https://github.com/cypress-io/cypress/issues/23677. If it doesn't work with libraries yet I will stop battling with it for now. If it doesn't work, what are you using to test libraries?
- Finally promising Web Testing solution
-
Episode 23/27: NgRx 16.1 & Signal Store, Jest, Cypress, Nx
Cypress Release Notes
- Trouble/Weirdness with accessing aliased values in `this` context
What are some alternatives?
react - A declarative, efficient, and flexible JavaScript library for building user interfaces.
Playwright - Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
cypress-esbuild-preprocessor - Bundle Cypress specs using esbuild
Detox - Gray box end-to-end testing and automation framework for mobile apps
appsyncmasterclass-backend - Backend for a Twitter Clone built with Serverless Framework, JS, AWS AppSyc, Lambda, DynamoDB & Cognito.
jest - Delightful JavaScript Testing.
kafka-test-helper - Utility library that simplify testing of Node.js components that interacts with Kafka broker.
supertest - 🕷 Super-agent driven library for testing node.js HTTP servers using a fluent API. Maintained for @forwardemail, @ladjs, @spamscanner, @breejs, @cabinjs, and @lassjs.
Sentry - Developer-first error tracking and performance monitoring
WebdriverIO - Next-gen browser and mobile automation test framework for Node.js
TestCafe - A Node.js tool to automate end-to-end web testing.
jasmine - Simple JavaScript testing framework for browsers and node.js