betterer
vitest
betterer | vitest | |
---|---|---|
5 | 110 | |
563 | 11,873 | |
- | 2.0% | |
4.3 | 9.8 | |
16 days ago | 4 days ago | |
TypeScript | TypeScript | |
MIT License | 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.
betterer
-
How to Effortlessly Improve a Legacy Codebase Using Robots
We first took a shot at addressing this gradually using a tool called Betterer, which works by taking a snapshot of the state of a set of errors, warnings, or undesired regular expressions in the codebase and surfacing changes in pull request diffs. Betterer had served us well in the past, such as when it helped us deprecate the Enzyme testing framework in favor of React testing library. However, because there were so many instances of noImplicitAny errors in the codebase, we found that much like snapshot tests, reviewers had begun to ignore Betterer results and we weren’t in fact getting better at all. Begrudgingly, we removed the rule from our Betterer tests and agreed to find a different way to enforce it. Luckily, this decision took place just in time for Snoosweek (Reddit’s internal hack week) so I was able to invest a few days into adding a new automation step to ensure incremental progress toward adherence to this rule.
-
Betterer v5.0.0 5️⃣
Check out the beast of a PR here (and yes, it took me three branches to get it right 😅)
-
Incrementally adding Stylelint rules with Betterer
I just released v4.0.0 of Betterer 🎉 (now with sweet new docs!) and it has a bunch of simplified APIs for writing tests. And just before I shipped it, I got an issue asking how to write a Stylelint test, so let's do it here and explain it line by line:
-
Conventions Don’t Matter – What Matters Is Consistency
You may think that is a bad idea, and stops innovation and adopting new trends and technologies. I dare to disagree. New conventions can be agreed on, and when a new convention is agreed on, it should be used in the codebase from that day on. Either by refactoring the whole code base to follow the new convention, which should be doable if the previous convention was followed carefully, or by using tools such as phenomnomnominal/betterer to incrementally adopt a new convention, and stop anyone from adding new code that does not follow the newly agreed convention. It is equally important to document the agreed conventions and keep the documentation up-to-date over time in addition to making sure everyone on the team hears about and understands the agreed conventions.
-
Lazy debug logging for Node.js
I have a tool that I've been working on for a while, and debugging it can be kind of a pain - especially when it's running inside VS Code. It'd be nice to have an easy way to get information about what is going on when the tool runs, without having to manually write a bunch of debug logging code and release a new version. That means that the usual approaches are not going to work:
vitest
-
Integration Testing in Obsidian
Using something like Vitest, Jest, or Mocha didn't work because:
-
Easier TypeScript API Testing with Vitest + MSW
However, I discovered a great combination that transformed my API call testing in TypeScript: Vitest and Mock Service Worker (MSW). Their well-crafted design makes them incredibly easy to use, enhancing the overall testing experience.
-
Vitest In-Source Testing for SFC in Vue?
Next we’ll install Vitest and happy-dom to the project by running:
-
Creating a reusable Design System between React and React Native with Tamagui
vitest is a testing framework similar to jest that integrates well with projects using Vite. It allows us to reuse plugins and configurations already set up in the vite.config.ts, making the test setup process easier.
- Criando um Design System reutilizável entre React e React Native com Tamagui
-
Test your React Apps with Vitest
For more detailed information on Vitest, refer to the official documentation. fficient Testing in Your React Projects with Vitest.
-
Um júnior e um teste técnico: The battle.
Vitest
-
Migrating from Jest to Vitest for your React Application
Are you looking to migrate from Jest to Vitest for your React application? Look no further.
-
Faster testing with Angular and Vitest ⚡️
In addition to those tools, a new testing framework has emerged named Vitest. Vitest is built on top of Vite and has many exciting features to keep improving the overall developer experience for writing tests. This post shows you how to set up Vitest in your existing Angular project.
- What’s your Vue application testing strategy?
What are some alternatives?
peeky - A fast and fun test runner for Vite & Node 🐈️ Powered by Vite ⚡️
jest - Delightful JavaScript Testing.
n - Node version management
Playwright - Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
unimported - Find and fix dangling files and unused dependencies in your JavaScript projects.
swc - Rust-based platform for the Web
action-junit-report - Reports junit test results as GitHub Pull Request Check
ava - Node.js test runner that lets you develop with confidence 🚀
WebdriverIO - Next-gen browser and mobile automation test framework for Node.js
happy-dom - A JavaScript implementation of a web browser without its graphical user interface
rut - ⚛️ React testing made easy. Supports DOM and custom renderers.
Next.js - The React Framework