Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
You should only really care about mutation testing if your code coverage is relatively high. If your code coverage is 20% then mutation testing should not be your priority. We use mutation testing (mutant for Ruby, pitest for Java). mutant is pretty hassle-free but only works when running under MRI so if you use jruby you are out of luck. pitest was far less easy to integrate.
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a more popular project.
Related posts
- Mutant – Automated code reviews via mutation testing – semantic code coverage
- Automated code reviews via mutation testing - semantic code coverage.
- Semantic blind spot in Ruby case statement
- What questions do you consider important for a Ruby on Rails technical interview?
- Run 1 hour test suite in 2 min with optimal parallelisation on existing CI infra