rspec-turbo runs your RSpec suite across N processes like parallel_tests, but balances work by actual example count (from a single --dry-run) using an LPT bin-packing heuristic, splitting oversized files across workers. It ships a live TTY dashboard, a CI-friendly progress mode, schema-fingerprinted test DB setup caching, JUnit output, coverage merging, and a slowest folders/files report.
🚀 turbo_tests2` is an RSpec parallel test runner. It uses runtime_groups for process counts, pid bookkeeping, file grouping, and runtime balancing, and replaces interleaved worker output with incremental summarized RSpec reporting. Source code of `turbo_test2` gem is based on Discourse and Rubygems work in this area (see README.md).
Minitest reporter that captures test results for TDD Guard validation.
Hen'i-tai (変異体) is a mutation testing framework for Ruby 3.3.6+. It produces Stryker-compatible mutation-testing-report-schema JSON, integrates with the Stryker Dashboard, and ships with a standalone HTML report powered by mutation-testing-elements. A free, open-source alternative to the mutant gem — with built-in cost-reduction strategies, per-test coverage analysis, and CI/CD integration out of the box.
A clean, well-tested FFmpeg wrapper with modern Ruby conventions, proper error handling, and zero dependencies. Features include metadata extraction, transcoding with progress reporting, scene detection, keyframe extraction, and Rails/Active Storage integration. Tested against FFmpeg 4, 5, 6, and 7.
Runs package E2E scenarios through agents with reproducible setup, sandbox isolation, and structured reports for reliable validation workflows.
Wraps Minitest with smart grouping, cross-package resolution, and persistent reports so developers and coding agents can run focused checks, diagnose failures with context, and retain searchable execution history.
Opinionated local CI that checks your code before it leaves your machine. After every commit a git hook runs four stages in a worktree at that commit: lint and build in parallel, then a fast suite, with a slow suite in the background, each held to a strict time budget (30 s, 30 s, 10 s and 5 minutes). The pre-push hook stops a push whose lint, build or fast suite failed. There are two ways in. People watch fun-ci console, a terminal dashboard drawn in 24-bit colour by a Rust renderer (included in the Linux and macOS gems), where each milestone of a run plays a scene of its own: a rocket while it runs, gears when the build passes, fireworks or a sunrise when the whole run does, an explosion when it fails, and a quiet night scene when nothing has run for a while. Coding agents and scripts ask with commands that answer in exit codes: fun-ci wait blocks until a commit's verdict is in, and fun-ci why prints what was kept about a failure (the failures a test runner reported, excerpts picked out by presets for 34 tools, log lines, the end of the output, with secrets masked), so nobody has to run a suite again to see what broke. Results are kept in SQLite. Any language works, since the stages are shell scripts; fun-ci init writes them for Ruby, Gradle, Maven, Rust, Go, Elixir, Dart, Swift, PHP, .NET, Python, Deno, Bun, Node, Perl, and C and C++ built with CMake or make.
A simple CLI tool to balance RSpec tests across parallel CI nodes using RSpec JSON reports
REST API for electronic invoicing in France: Factur-X (CII), UBL 2.1, AFNOR PDP/PA, electronic signatures. ## 🎯 Main Features ### 📄 Invoice Generation - **Formats**: CII XML, UBL 2.1 XML, or Factur-X PDF/A-3 - **Profiles** (CII/PDF): MINIMUM, BASIC, EN16931, EXTENDED - **UBL**: Always EN16931 compliant - **Standards**: EN 16931 (EU directive 2014/55), ISO 19005-3 (PDF/A-3), CII (UN/CEFACT), UBL 2.1 (OASIS) - **Simplified Format**: Generation from SIRET + auto-enrichment (Chorus Pro API + Business Search) ### ✅ Factur-X - Validation - **XML Validation**: Schematron (45 to 210+ rules depending on profile) - **PDF Validation**: PDF/A-3, Factur-X XMP metadata - **VeraPDF**: Strict PDF/A validation (146+ ISO 19005-3 rules) ### ✍️ Electronic Signature - **Standards**: PAdES-B-B, PAdES-B-T (RFC 3161 timestamping), PAdES-B-LT (long-term archival) - **eIDAS Levels**: SES (self-signed), AdES (commercial CA), QES (QTSP) - **Validation**: Cryptographic integrity and certificate verification ### 📋 Flux 6 - Invoice Lifecycle (CDAR) - **CDAR Messages**: Acknowledgements, invoice statuses - **PPF Statuses**: REFUSED (210), PAID (212) ### 📊 Flux 10 - E-Reporting - **Tax Declarations**: International B2B, B2C - **Flow Types**: 10.1 (B2B transactions), 10.2 (B2B payments), 10.3 (B2C transactions), 10.4 (B2C payments) ### 📡 AFNOR PDP/PA (XP Z12-013) - **Flow Service**: Submit and search flows to PDPs - **Directory Service**: Company search (SIREN/SIRET) - **Multi-client**: Support for multiple PDP configs per user ### 🏛️ Chorus Pro - **Public Sector Invoicing**: Complete API for Chorus Pro ### ⏳ Async Tasks - **Celery**: Asynchronous generation, validation and signing - **Polling**: Status tracking via `/tasks/{task_id}/status` - **Webhooks**: Automatic notifications when tasks complete ## 🔒 Authentication All requests require a **JWT token** in the Authorization header: ``` Authorization: Bearer YOUR_JWT_TOKEN ``` ### How to obtain a JWT token? #### 🔑 Method 1: `/api/token/` API (Recommended) **URL:** `https://factpulse.fr/api/token/` This method is **recommended** for integration in your applications and CI/CD workflows. **Prerequisites:** Having set a password on your account **For users registered via email/password:** - You already have a password, use it directly **For users registered via OAuth (Google/GitHub):** - You must first set a password at: https://factpulse.fr/accounts/password/set/ - Once the password is created, you can use the API **Request example:** ```bash curl -X POST https://factpulse.fr/api/token/ \ -H "Content-Type: application/json" \ -d '{ "username": "your_email@example.com", "password": "your_password" }' ``` **Optional `client_uid` parameter:** To select credentials for a specific client (PA/PDP, Chorus Pro, signing certificates), add `client_uid`: ```bash curl -X POST https://factpulse.fr/api/token/ \ -H "Content-Type: application/json" \ -d '{ "username": "your_email@example.com", "password": "your_password", "client_uid": "550e8400-e29b-41d4-a716-446655440000" }' ``` The `client_uid` will be included in the JWT and allow the API to automatically use: - AFNOR/PDP credentials configured for this client - Chorus Pro credentials configured for this client - Electronic signature certificates configured for this client **Response:** ```json { "access": "eyJ0eXAiOiJKV1QiLCJhbGc...", // Access token (validity: 30 min) "refresh": "eyJ0eXAiOiJKV1QiLCJhbGc..." // Refresh token (validity: 7 days) } ``` **Advantages:** - ✅ Full automation (CI/CD, scripts) - ✅ Programmatic token management - ✅ Refresh token support for automatic access renewal - ✅ Easy integration in any language/tool #### 🖥️ Method 2: Dashboard Generation (Alternative) **URL:** https://factpulse.fr/api/dashboard/ This method is suitable for quick tests or occasional use via the graphical interface. **How it works:** - Log in to the dashboard - Use the "Generate Test Token" or "Generate Production Token" buttons - Works for **all** users (OAuth and email/password), without requiring a password **Token types:** - **Test Token**: 24h validity, 1000 calls/day quota (free) - **Production Token**: 7 days validity, quota based on your plan **Advantages:** - ✅ Quick for API testing - ✅ No password required - ✅ Simple visual interface **Disadvantages:** - ❌ Requires manual action - ❌ No refresh token - ❌ Less suited for automation ### 📚 Full Documentation For more information on authentication and API usage: https://factpulse.fr/documentation-api/
Battle-tested documentation SPECIFICALLY for the Clockify Detailed Reports API endpoint (POST /reports/detailed) with 43+ documented errors, corrections to official documentation, and complete parameter reference. NOT general Clockify API docs - just the detailed reports endpoint. More accurate than official Clockify documentation.
Ruby gem to generate automated test reports for academic assignments with HTML templates, CSV export, optional PDF (via prawn), class-wide reporting, and basic Jaccard code similarity.
A simple testing library that works on ruby and mruby. This has been designed to be very modular, you can run different types of suites with different setup/teardown and before/after blocks. You can have as many reporters as you want, these can range from "output to the terminal in a nice way" all the way to "shape the results into an XML or JSON for my CI". The secondary purpose of this testing library is to work with mruby for my game engine Taylor and any project built upon that. I also plan to support quite a few ruby versions as I want the code for this to be very portable. The main feature I don't want to drop is positional AND keyword arguments in definitions, this means anything that matches the Ruby 2.6+ spec should be compatible.
Inferno test kit for testing systems per the Central Cancer Registry Reporting IG
This gem is deprecated and has been replaced by 'ruby_test_student_grader'. The new name is clearer and future maintenance and improvements will happen there. You can still use this gem, but we strongly recommend migrating. More info: https://rubygems.org/gems/ruby_test_student_grader
Run performance tests, generate reports and more using JMeter
# Cryptophysh My attempt to produce a solution to the requirements listed [here](https://github.com/krystal/code-tasks/blob/main/password-generator.md). Essentially, a library/gem you can include in to your own code to add a `::generate_password` class method on a class. I've pushed the built gem up to RubyGems for completeness' sake. ## Installation Install the gem and add to the application's Gemfile by executing: $ bundle add cryptophysh If bundler is not being used to manage dependencies, install the gem by executing: $ gem install cryptophysh ## Usage ### Extending your own class `require cryptophysh` and Add to your class: `extend Cryptophysh` Your class will now have access to the `::generate_password` class method. ### Using the Cryptophysh::PasswordGenerator Class See the YARD documentation on the class itself for details. ## Development After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment. To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org). ## Contributing Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/cryptophysh. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/kryptykphysh/cryptophysh/blob/master/CODE_OF_CONDUCT.md). ## License The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT). ## Code of Conduct Everyone interacting in the Cryptophysh project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/kryptykphysh/cryptophysh/blob/master/CODE_OF_CONDUCT.md).
IrtRuby is a Ruby library for Item Response Theory (IRT) analysis, commonly used in educational assessment, psychological testing, and survey research. Features three core IRT models: • Rasch Model (1PL) - Simple difficulty-only model • Two-Parameter Model (2PL) - Adds item discrimination • Three-Parameter Model (3PL) - Includes guessing parameter Key capabilities: • Joint maximum likelihood by gradient ascent with an adaptive learning rate • Convergence reporting, scale identification, and exclusion of extreme response patterns • Missing data strategies (ignore, treat as incorrect/correct) • Performance and convergence benchmark scripts Intended for researchers, data scientists, and developers working with educational assessments, psychological measurements, or any binary response data where item and person parameters need to be estimated simultaneously.
Towel collects test results as they run, reporting them to towel.dev for easier inspection, debugging, and sharing.
Open Android Emeulators Then Generate Report File From Tests then Upload the File To Slack
Danger runs on CI and reports common code review chores, code quality and test coverage.
I am testing for brandjacking vulnerabilities in products that are in bug bounty programs. This code is reporting-only, and does not do anything malicious.
Writes a VSTest report for spectre test run, which can be used in Azure DevOps
Writes an interactive HTML report for spectre test runs
Writes a JUnit report for spectre test run, which can be used for e.g. Jenkins
test-unit-launchable is a convinient plugin for test-unit that generates a Launchable test report file based on the test results.
The Siyousho gem is designed to facilitate End-to-End (E2E) testing by automatically generating detailed specification documents. These documents are enriched with screenshots, providing a visual context for each testing step. Ideal for developers and QA teams who require comprehensive test reports, this gem helps in capturing the state of the application at various stages of the testing cycle.