jsverify
ava
jsverify | ava | |
---|---|---|
5 | 34 | |
1,666 | 20,623 | |
0.1% | 0.1% | |
1.8 | 8.0 | |
about 3 years ago | 5 days ago | |
JavaScript | JavaScript | |
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.
jsverify
-
The 5 principles of Unit Testing
Libraries like JSVerify or Fast-Check offer essential tools to facilitate property-based testing.
-
Ask HN: What's your favorite software testing framework and why?
I tend to use anything that offers property-testing, since tests are much shorter to write and uncover lots more hidden assumptions.
My go-to choices per language are:
- Python: Hypothesis https://hypothesis.readthedocs.io/en/latest (also compatible with PyTest)
- Scala: ScalaCheck https://scalacheck.org (also compatible with ScalaTest)
- Javascript/Typescript: JSVerify https://jsverify.github.io
- Haskell: LazySmallCheck2012 https://github.com/UoYCS-plasma/LazySmallCheck2012/blob/mast...
- When I wrote PHP (over a decade ago) there was no decent property-based test framework, so I cobbled one together https://github.com/Warbo/php-easycheck
All of the above use the same basic setup: tests can make universally-quantified statements (e.g. "for all (x: Int), foo(x) == foo(foo(x))"), then the framework checks that statement for a bunch of different inputs.
Most property-checking frameworks generate data randomly (with more or less sophistication). The Haskell ecosystem is more interesting:
- QuickCheck was one of the first property-testing frameworks, using random genrators.
- SmallCheck came later, which enumerates data instead (e.g. testing a Float might use 0, 1, -1, 2, -2, 0.5, -0.5, etc.). That's cute, but QuickCheck tends to exercise more code paths with each input.
- LazySmallCheck builds up test data on-demand, using Haskell's pervasive laziness. Tests are run with an error as input: if they pass, we're done; if they fail, we're done; if they trigger the error, they're run again with slightly more-defined inputs. For example, if the input is supposed to be a list, we try again with the two forms of list: empty and "cons" (the arguments to cons are both errors, to begin with). This exercises even more code paths for each input.
- LazySmallCheck2012 is a more versatile "update" to LazySmallCheck; in particular, it's able to generate functions.
-
Property Based Testing Framework for Node
The usage of hypothesis is very intuitive and simple, and presents the concept of property-based testing perfectly. So I also wanted to find an equivalent alternative in Node. Two of them have high star ratings on Github, JSVerify with 1.6K stars and fast-check with 2.8K stars. So I took some time to study fast-check a little bit and try to get closer to my daily work.
-
Machine Readable Specifications at Scale
Systems I've used for this include https://agda.readthedocs.io/en/v2.6.0.1/getting-started/what... https://coq.inria.fr https://www.idris-lang.org and https://isabelle.in.tum.de
An easier alternative is to try disproving the statement, by executing it on thousands of examples and seeing if any fail. That gives us less confidence than a full proof, but can still be better than traditional "there exists" tests. This is called property checking or property-based testing. Systems I've used for this include https://hypothesis.works https://hackage.haskell.org/package/QuickCheck https://scalacheck.org and https://jsverify.github.io
-
React to Elm Migration Guide
Using create-react-app, you’ll run npm test which uses Jest internally. If you are dealing with a lot of data on the UI, or using TypeScript, use JSVerify for property tests. For end to end tests, Cypress is a great choice.
ava
-
Painless CLI integration testing
We use Jest Framework for testing. Jest is not a dogma, and, of course, in its place can be any other test runner, such as Mocha or Ava. Let's focus on tests. I'll provide a short example because I don’t want to waste your time. You can find the full version here. It's crucial to read the comments in the code below. Let's go!
-
Speeding up the JavaScript ecosystem – The barrel file debacle
> In the popular jest test runner, each test file is executed in its own child process.
Is that confirmed?
I've been following this issue:
https://github.com/jestjs/jest/issues/6957
And what Jest actually does is still kind of muddy.
In contrast to that, other test runners like AVA have a clear description what happens when:
https://github.com/avajs/ava/blob/main/docs/01-writing-tests...
-
What Tools Are You Using to Test Your Code?
I've been looking at using japa or ava for web server testing but was curious what others were using and why.
-
[2023-07-14] Razuberi Development Update
Continued work on the test suite. Implementing AVA, with snapshotting. Making a lot of effort to have the snapshot directory structure match the test262 test directory structure by generating AVA test files.
-
Ask HN: What's your favorite software testing framework and why?
You might want to give ava a spin:
https://github.com/avajs/ava/
It has a TAP reporter, but more importantly, as opposed to the more popular solutions, like Jest, the way it achieves parallelism is explained in the docs and won't change anytime soon, thus preventing wonky, hard to debug errors which occur when this part is abstracted away.
-
The new React's documentation
I switched to ava for that reason and have been very happy with it. But vitest looks nice, too. Thanks for the pointer.
-
How to create and publish a TypeScript library with ease
Runs unit tests using AVA.
-
Express API Testing
Last but not least important are ava, uvu and tape; they are a really light and fast test runners.
-
Unit testing: What to use, and how?
I've had some good experiences with Ava + Sinon. I've personally disliked Jest because it seemed to do some weird trickery in the background that prevented me from using ES modules.
-
Tech stack discussion
Ava for a simpler environment than Jest, which I usually use. I need to check how to mock ESM with it, though.
What are some alternatives?
greenlight - Clojure integration testing framework
jest - Delightful JavaScript Testing.
testy - test helpers for more meaningful, readable, and fluent tests
ocapi-proxy - Salesforce Commerce Cloud Node.js OCAPI Proxy Router
LazySmallCheck2012 - Lazy SmallCheck with functional values and existentials!
vitest - Next generation testing framework powered by Vite.
fast-check - Property based testing framework for JavaScript (like QuickCheck) written in TypeScript
tape - tap-producing test harness for node and browsers
hitchstory - Type-safe YAML integration tests. Tests that write your docs. Tests that rewrite themselves.
mocha - ☕️ simple, flexible, fun javascript test framework for node.js & the browser
datadriven - Data-Driven Testing for Go
tap - Test Anything Protocol tools for node