betterer
betterer makes it easier to make incremental improvements to your codebase (by phenomnomnominal)
rut
⚛️ React testing made easy. Supports DOM and custom renderers. (by milesj)
SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
surveyjs.io
featured
| betterer | rut | |
|---|---|---|
| 5 | - | |
| 563 | 14 | |
| - | - | |
| 4.3 | 2.1 | |
| 16 days ago | over 2 years ago | |
| TypeScript | TypeScript | |
| MIT License | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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
Posts with mentions or reviews of betterer.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-01.
-
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:
rut
Posts with mentions or reviews of rut.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning rut yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
When comparing betterer and rut you can also consider the following projects:
peeky - A fast and fun test runner for Vite & Node 🐈️ Powered by Vite ⚡️
Enzyme - JavaScript Testing utilities for React
vitest - Next generation testing framework powered by Vite.
jest - Delightful JavaScript Testing.
n - Node version management
ui-harness - Create, isolate and test modular UI components in React.
unimported - Find and fix dangling files and unused dependencies in your JavaScript projects.
react-testing-library - 🐐 Simple and complete React DOM testing utilities that encourage good testing practices.
action-junit-report - Reports junit test results as GitHub Pull Request Check
chai-enzyme - Chai.js assertions and convenience functions for testing React Components with enzyme
WebdriverIO - Next-gen browser and mobile automation test framework for Node.js
legit-tests - Chainable, easy to read, React testing library