Open Source Ruby Performance Testing Software for Windows

Marathon provides an integrated environment for test script creation and execution. Supported FW: Web, Java Swing/ Java FX. Currently, Marathon supports JRuby script models for recording the test scripts.Marathon test runner generates Allure test reports.Marathon allows for grouping of test cases.It also has an option of inserting modules while recording(in MarathonITE while recording). It allows tester to inset checklist while recording and also takes screen capture and annotate it in playing the test cases. Extraction of code into modules and inserting it is very easy using marathon.It has different themes of UI which attracts tester to do work on it. Object mapping is quite simple and configuring is very easy for tester to understand and do the work. Debugging of test scripts is also easy and has script console which takes selenium commands. Slow play of test cases is also available.It allows to create multiple fixtures for different types of tests.

Modern concurrency tools including agents, futures, promises, thread pools, supervisors, and more. Inspired by Erlang, Clojure, Scala, Go, Java, JavaScript, and classic concurrency patterns. Concurrent Ruby is an 'unopinionated' toolbox that provides useful utilities without debating which is better or why. It remains free of external gem dependencies. It stays true to the spirit of the languages providing inspiration, but implements in a way that makes sense for Ruby. Keeps the semantics as idiomatic Ruby as possible, supports features that make sense in Ruby. Excludes features that don't make sense in Ruby. It is small, lean, and loosely coupled, thread-safety, and with backward compatibility. Concurrent Ruby makes one of the strongest thread safety guarantees of any Ruby concurrency library, providing consistent behavior and guarantees on all four of the main Ruby interpreters (MRI/CRuby, JRuby, Rubinius, TruffleRuby).

BenchLab is a Web Application benchmarking framework using real web browsers.

RSpec Rails brings the RSpec testing framework to Ruby on Rails as a drop-in alternative to its default testing framework, Minitest. In RSpec, tests are not just scripts that verify your application code. They’re also specifications (or specs, for short): detailed explanations of how the application is supposed to behave, expressed in plain English. RSpec follows semantic versioning, which means that “major version” upgrades (e.g., 2.x → 3.x) come with breaking changes. If you’re upgrading from version 2.x or below, read the rspec-rails upgrade notes to find out what to watch out for. In RSpec, assertions are called expectations, and every expectation is built around a matcher. When you expect(a).to eq(b), you’re using the eq matcher. RSpec Rails defines ten different types of specs for testing different parts of a typical Rails application. Each one inherits from one of Rails’ built-in TestCase classes, meaning the helper methods provided by default in Rails tests are available.