PropCheck vs Rantly
PropCheck
github.comRantly
github.comSide by side
| Figure | PropCheck | Rantly |
|---|---|---|
| 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.3 (#17) |
| License | The project is released under the MIT License. | The project code is published under the MIT License. |
| Purpose | PropCheck is a Ruby library for property-based testing that checks assertions against generated inputs. | Rantly generates random test data and provides a Test::Unit extension for property-based testing. |
| Ruby requirement | The gem requires Ruby version 2.5.1 or later. | The repository README says Rantly requires Ruby 3.2 or higher. |
| Shrinking | When a generated case fails, PropCheck attempts to simplify it to a minimal counterexample. | Optional shrinking can reduce failing values; the documented search is limited to at most 1024 shrinking operations and does not fully traverse the failure tree. |
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.