mutant
Ruby-JMeter
Our great sponsors
| mutant | Ruby-JMeter | |
|---|---|---|
| 5 | 2 | |
| 1,925 | 750 | |
| - | -0.3% | |
| 8.2 | 0.0 | |
| 6 days ago | 6 months ago | |
| Ruby | Ruby | |
| Nonstandard | 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.
mutant
-
An ex-Googler's guide to dev tools
There's a pretty good Ruby gem I've used for this before:
https://github.com/mbj/mutant
-
Code coverage vs mutation testing.
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.
- 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
mutant shows redundant semantics, why we'd like to reduce them is perhaps better explained at https://github.com/mbj/mutant#what-is-mutant
Ruby-JMeter
-
Load Testing with Ruby-JMeter
Here comes the ruby-jmeter! An easy to use tool that helps you to write readable test plans, which leads to focusing on your simulator scenarios to become closer to real customer behaviours. Under the hood, it uses JMeter. The code below simulates 10 customers keep visiting Google while its being run.
-
Load Testing: An Unorthodox Guide
JMeter is old and crusty and not at all friendly to work with. But I used it for years because it was really about the best we had. Today I don't wish it on anyone.
Ruby JMeter finally made JMeter easier to manage, but I haven't worked in a Ruby shop for years, and I'm not going to force everyone to learn Ruby just to do some load testing.
https://github.com/flood-io/ruby-jmeter
Then along came k6. It's developer-friendly and I've seen people actually enjoy using it. I recommend anyone considering JMeter also take a look at k6. They do a better job of selling it than I do:
https://k6.io
I am also Gatling-curious. Seems like an option for anyone in the JVM ecosystem.
https://gatling.io
What are some alternatives?
Spring - Rails application preloader
Parallel Tests - Ruby: 2 CPUs = 2x Testing Speed for RSpec, Test::Unit and Cucumber
vcr - Record your test suite's HTTP interactions and replay them during future test runs for fast, deterministic, accurate tests.
Zapata - An Automatic Automated Test Writer
rspec-side_effects - RSpec extension for checking the side effects of your specifications.
power_assert - Power Assert for Ruby
timecop - A gem providing "time travel", "time freezing", and "time acceleration" capabilities, making it simple to test time-dependent code. It provides a unified method to mock Time.now, Date.today, and DateTime.now in a single call.
Appraisal - A Ruby library for testing your library against different versions of dependencies.
Wrong - Wrong provides a general assert method that takes a predicate block. Assertion failure messages are rich in detail.