Testmo Integrations
DocsIntegrationsREST APIBack to Testmo
  • Integrations
  • Major Tools
    • Jira
    • GitHub
    • GitLab
  • CI/CD
    • Azure Pipelines
    • Bitbucket
    • CircleCI
    • GitHub Actions
      • GitHub Jobs
    • GitLab CI/CD
      • GitLab Jobs
    • Jenkins
    • ➕Custom CI
  • Issue Trackers
    • Asana
    • Azure DevOps
    • ClickUp
    • GitHub Issues
    • GitLab Issues
    • Jira Cloud
    • Jira Server/DC
    • Linear
    • Monday.com
    • Redmine
    • Shortcut
    • Trac
    • Trello
    • YouTrack
    • ➕Custom Links
  • Automation
    • Appium
    • BrowserStack
    • Catch
    • Cucumber
    • Cypress
    • GoogleTest
    • Jasmine
    • Jest
    • JUnit
    • Minitest
    • Mocha / JavaScript
    • Nightwatch.js
    • NUnit
    • PHPUnit
    • Playwright
    • Postman
    • Pytest
    • Robot Framework
    • RSpec
    • Sauce Labs
    • Selenium
    • Testim
    • TestNG
    • WebdriverIO
    • XCTest / Xcode
    • xUnit.net
    • ➕More Tools
  • Enterprise auth
    • Azure & AD
    • Google
    • Okta
    • OneLogin
    • ➕Custom SAML
Powered by GitBook
On this page
  • Run minitest & generate XML file
  • Submit test results to Testmo
  • Bonus: Launch minitest with Testmo CLI
  • More resources & references

Was this helpful?

  1. Automation

Minitest

PreviousJUnitNextMocha / JavaScript

Last updated 2 years ago

Was this helpful?

Testmo works with any test automation tool, including the popular BDD & unit testing framework for Ruby. This quickstart guide provides an overview of how to report minitest & Ruby test automation results to Testmo.

Run minitest & generate XML file

test_helper.rb
require "minitest/reporters"
Minitest::Reporters.use! Minitest::Reporters::JUnitReporter.new(:reports_dir => "results")
$ rake test
$ npm install -g @testmo/testmo-cli
$ testmo -h

Usage: testmo [options] [command]
[...]
$ export TESTMO_TOKEN=********
$ testmo automation:run:submit \
  --instance https://<your-name>.testmo.net \
  --project-id 1 \
  --name "Minitest test run" \
  --source "unittests" \
  --results results/*.xml

If you run this example on a single command line, make sure to remove the backspaces:

$ export TESTMO_TOKEN=********
$ testmo automation:run:submit --instance https://<your-name>.testmo.net --project-id 1 --name "Minitest test run" --source "unittests" --results results/*.xml

On Windows, the command line uses a slightly different syntax to set a variable:

> set TESTMO_TOKEN=********
> testmo automation:run:submit --instance https://<your-name>.testmo.net --project-id 1 --name "Minitest test run" --source "unittests" --results results/*.xml
See command output
Collecting log files ..
Found 1 result file with a total of 855 tests
Created new automation run (ID: 254)
Created new thread (ID: 608)
Sending tests to Testmo ..
Uploading: [|||||||||||||||||||||||||] 100% | ETA: 0s | 855/855 tests
Successfully sent tests and completed run
Marked the run as completed  

That's it! 🎉 This will automatically analyze the XML result file, create a new test run in Testmo, submit all tests & results and mark the run as completed. There's no need to manually create any tests, map tests or IDs or build any custom API code. Everything is handled automatically for you.

In the above example, we first launched minitest to generate the XML file and then used our CLI tool to submit the results in a second step. As an improvement to the above example, we can ask our CLI tool to launch minitest (testmo then starts and waits for minitest to finish). This has the following additional benefits:

a) Capture full console output and send it to Testmo b) Accurately measure test times c) Record the minitest exit code

Launch minitest with CLI tool

We can ask our CLI tool to launch minitest, so we can capture the console output and more:

$ export TESTMO_TOKEN=********
$ testmo automation:run:submit \
  --instance https://<your-name>.testmo.net \
  --project-id 1 \
  --name "Minitest test run" \
  --source "unittests" \
  --results results/*.xml \
  -- rake test
    ^ space!

Now that you are familiar with submitting your minitest & Ruby test results to Testmo, you might also find the following additional examples, topics and references useful for more advanced workflows.

Minitest can generate JUnit-style XML files, which has become a standard format to exchange test results between tools. You simply need to install the gem and configure the JUnitReporter reporter in your test_helper.rb file.

This will run your minitest tests and automatically write all test results to XML files in the results directory. You can learn more in the .

Submit test results to Testmo

To submit your test results to Testmo, you simply use our cross-platform CLI tool. The CLI tool is distributed as an NPM package and is easy to install on any system. Simply install our official @testmo/testmo-cli NPM package:

We can now send the minitest test results to Testmo. To do this, make sure to in Testmo from your profile page. The API key is used to authenticate with Testmo to send the results. We can then use the testmo CLI tool so submit our results (note that we first set the TESTMO_TOKEN variable, which the tool expects):

Bonus: Launch minitest with Testmo CLI

Also learn more and see other examples in the full .

More resources & references

➡️
minitest-reporters
gem's documentation
testmo
generate an API key
Testmo CLI guide
Testmo automation overview
Testmo automation concepts
Integrating with CI/CD pipelines
Testmo CLI guide and reference
Automation tool examples
minitest