elm-test-rs
test
elm-test-rs | test | |
---|---|---|
5 | 3 | |
74 | 233 | |
- | 0.9% | |
1.4 | 5.4 | |
7 months ago | 2 months ago | |
Rust | Elm | |
BSD 3-clause "New" or "Revised" License | BSD 3-clause "New" or "Revised" 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.
elm-test-rs
-
elm-test and elm-test-rs
So I'm super interested in knowing more about your setup that makes it so much faster for elm-test than elm-test-rs. Would you mind open an issue in https://github.com/mpizenberg/elm-test-rs ?
-
Setting up an Elm project in 2022
To actually run the tests, however, there are currently two options. The first, as noted above, is node-test-runner, which is available from npm at elm-test. This utility will run the tests as defined in your Elm code, and return the results. There is a second option, elm-test-rs, which is written in Rust instead of Node. It has a handful of features that node-test-runner does not have, as well as some downsides (see the Github README for details), but in general both tools work very well for testing Elm code.
- Version 1.2 of elm-test-rs released (alternative to elm-test) with native ARM and Deno support
- Announcing elm-test-rs 1.0.0, a new tests runner for the Elm language, built in Rust
-
Announcing elm-test-rs 1.0.0, a fast and portable executable to run your Elm tests!
More info in the readme at https://github.com/mpizenberg/elm-test-rs
test
-
Setting up an Elm project in 2022
The de-facto standard for testing an Elm application is elm-test. However, as noted in the README:
-
Porting Elm to WebAssembly
Once all that handwritten C code was solid, I needed to make sure the C generated from Elm was working properly. I found the source for the core library's unit tests and decided to port them into my project and add some of my own tests. You can run the tests in WebAssembly in your browser too. (Funnily enough, one of the biggest challenges was getting the Elm Test framework itself to run! The framework is more complex than the tests themselves. I still need to come back to the fuzzer tests!)
-
Causing Bedlam in Elm
Lesson Learned: Elm has built in recursion improvements for a variety of positive reasons, and you should think in recursion to solve looping problems. Use property/fuzz tests and bounds checking with early exit to prevent this from locking up your UI (i.e if > 9000, omg abort). If you’re algorithm is reasonable, but the data set is just gigantic, offload to a server instead for more horsepower. Or Workers if you don’t have server chops, can’t upload the large data, or don’t trust your server devs. (“But Doc, I’m the server dev!” Good joke. Ever̸y̴b̸ody laugh. Roll on s̵͓̆nâ̶̱re drum. Curtains.)
What are some alternatives?
node-test-runner - Runs elm-test suites from Node.js. Get it with npm install -g elm-test
Google Test - GoogleTest - Google Testing and Mocking Framework
vite-elm-template - A default template for building Elm applications using Vite.
ut - C++20 μ(micro)/Unit Testing Framework
elm-review - Analyzes Elm projects, to help find mistakes before your users find them.
CppUTest - CppUTest unit testing and mocking framework for C/C++
vite-plugin-elm - A plugin for Vite enables you to compile an Elm application/document/element
Catch - A modern, C++-native, test framework for unit-tests, TDD and BDD - using C++14, C++17 and later (C++11 support is in v2.x branch, and C++03 on the Catch1.x branch)
test - Measuring Massive Multitask Language Understanding | ICLR 2021
Google Mock
editor-plugins - List of editor plugins for Elm.
benchmark - A microbenchmark support library