Usability Enhancements to the Tddium CLI

We’re happy to announce some changes to the “tddium” command — the main CLI interface to Tddium.

To pick up the changes, “gem update tddium” to get version 1.4.1 or later.

Watch the video tour:

[brightcove vid= 1627063974001&exp3=1554504229001&surl=http://c.brightcove.com/services&pubid= 1555356985001&pk=AQ~~,AAABaiKAJqk~,uHCuw6m0afMcd4N5Uhg1r07CY0oE6U0G&w=480&h=268]

1. “tddium run” – Automatic Suite Setup and Testing

TL;DR: “tddium run” automatically creates a suite (setup for CI) for the current branch.  No need to run “tddium suite” manually.

Tddium is built around the concept of test “suites” — the test files associated with a repo and a branch, along with other configuration data, so when we set out to build a CLI, we made the “tddium suite” command the first step a new user ran to create and configure a test suite, followed by “tddium spec” to start tests (back when we only supported RSpec).  The “tddium suite” command is the one-stop suite setup and configuration utility — it creates new suites, and lets you edit suite settings.

We soon discovered that many users who follow the common topic-branch (or feature-branch, or git-flow) methodology had to go through the suite setup procedure often, sometimes many times a day.  They would simply accept the defaults “tddium suite” automatically determined – for the test pattern used to select tests, the ruby version, and the CI origin URL, and then waiting for the suite update to persist in their Tddium git repo (“your git git repo is being prepped”) before starting tests.

We also found that new users were confused by the output and prompts from “tddium suite”.   Much of the copy produced by “tddium suite” was written before www.tddium.com had much content, so it had to be both utility and HOWTO.

So, we renamed “tddium spec” to “tddium run”, and made it a whole lot smarter:

  1. Automatically creates a new suite (and configures it for CI!) or chooses an existing one with sensible defaults.  To view or configure the suite, use the “tddium suite” command as before.
  2. Waits for your Tddium repo to be set up and automatically starts tests when it’s ready.
  3. Has better formatted warnings and status messages.

2. “tddium web” – Open the latest session in your browser

Instead of cutting and pasting a URL for a manual run from the CLI, you can use “tddium web” to automatically open your latest build in a browser.

3. Shared login across repos

Tddium used to require you to log on the CLI in once per repo – no more!

Now, your login is valid across all of your git repos.

Enjoy!

We’re busy working on more usability enhancements based on feedback from all of our great customers.

Don’t hesitate to send us questions, comments, or suggestions.

– The Tddium Team

Post a Comment