PropCheck vs Rapid
PropCheck
github.comRapid
pgregory.netSide by side
| Figure | PropCheck | Rapid |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Linux | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Property-Based Testing Tools | 8.0 (#7) | 7.1 (#18) |
| Dependencies | The README says PropCheck requires no external dependencies. | Rapid has no dependencies outside the Go standard library. |
| License | The project is released under the MIT License. | Rapid is licensed under the Mozilla Public License Version 2.0. |
| Stateful testing | The README lists stateful property testing as a possible future separate add-on library. | Rapid supports state machine testing. |
| What it does | PropCheck is a Ruby library for property-based testing that generates inputs and checks whether assertions hold across them. | Rapid is a Go library for property-based testing that checks user-defined properties against automatically generated test cases. |
Plans
In their own words
PropCheck
PropCheck is a Ruby library for property-based testing: it generates inputs and checks whether assertions hold across them. When a generated example fails, it tries to simplify that case into a smaller counterexample. Built-in generators cover integers, floats, strings, symbols, arrays, hashes, sets, dates, times and datetimes. A generator DSL lets developers define their own, while the API also supports mapping and binding values, alternatives and weighted frequency choices.
Before, after and around hooks provide setup and cleanup around generated examples. The README gives usage examples for RSpec, MiniTest, test-unit and vanilla Ruby, and says the library has no external dependencies. PropCheck requires Ruby 2.5.1 or later and is released under the MIT License. It is available as a free Community library. Installation can be done through a Gemfile or with `gem install prop_check`. For generated examples involving a database, the README recommends cleaning database state around each example and mentions DatabaseCleaner. Stateful property testing is described as a possible future separate add-on.