Nordic Pelican

This release introduces test sets which select a subset of testcases from a testplan. This way you can choose to run only a subset of your tests, e.g. if you just want to test a specific feature of your application or run something like a "bare minimum test set". See https://ruruku.sh/testplan/#test-set for details.

This change is backward compatible with Ruruku servers in the v0.4 line, however with a slightly reduced functionality. If you want to use testcase annotations (introduced in this version) you need a server in at least v0.4.3.

Nordic Otter

Bugfix release which supersedes v0.4.1:

• fixes a styling issue of the error message during login (def27bf)
• makes the testplan table header sticky (b42f344)
• fixes the participant count when claiming a testcase (ffbfbbf)
• fixes ruruku session describe (af523a4)
• enables autolinking in markdown fields so that URLs automatically become links (9c88891)
• removed the validation rule requiring testcase names to be at least 5 characters long (8d6150b)

Nordic Squid

Bugfix release for v0.4.0 - fixes #70, #71 and other minor issues when editing testcases (description, steps and must-pass would not update properly)

Nordic Coral

Use the v0.4.3 release instead - more functionality, fewer bugs

• This release introduces a long-standing issue: modifying the testcases of an ongoing session (#35). Sessions must be marked modifiable when they're started (using ruruku start --modifiable) so that users who posses the session.modify permission can alter them.
  

• Using modifiable sessions and the new ruruku plan from-session users can now create a testplan collaboratively (#59).

• The ruruku web client has keybindings now - use the h key to bring up a help dialog showing you what you can do. Most notably, there are keybindings for quickly contributing (speed testing).

• Sessions can be linked to directly now. Have a look at the links in the session detail view (#60):

• Implemented shell autocomplete for the ruruku CLI. Use . <(ruruku completion) to enable this feature (#62)
• Implemented a version command for the server and client: ruruku version (#67)
• Now handling CORS header correctly (#63)

Nightly

Nightly build of ruruku - might not work as expected

Full Manatee

This release sports a few UX improvements:

1. Better validation: previously invalid testplans resulted in a malfunctioning ruruku session (e.g. claim not working #52 or simply no testcases showing up). Now, the server validates a testplan properly before starting a session (see #53).
2. Better sidebar: previously the sidebar did not sport common elements across its different uses. For example, viewing a testcase compared to submitting the test result did not have a common way to close the sidebar. Also, the sidebar had a narrow 475px width; now users can choose to expand it to 60% of the screen width. Compare old with new

Funky Turtle

General

• Starting with this release one can attach annotations to sessions. Annotations are simple key-value pairs, for example commit= 04eeb33. The ruruku session start command got a new --annotations flag for specifying this metadata. The web client shows annotations in the upper right corner.

Web client

• Users can now change their password from within the web client
• Ruruku now requests a reload when a new version was downloaded by the service worker

Nihilist Guppy

This release introduces user management and proper authentication to Ruruku. With it come permissions, a renewed token handling mechanism and a whole bunch of minor bug fixes, improved test coverage and UX improvements.

A simple manual test coordinator

Usage:
  ruruku [command]

Available Commands:
  help        Help about any command
  plan        Creates a new testplan
  serve       Starts a ruruku API server
  session     Controls a test session/run
  start       Creates a ruruku API server and starts a session
  test        Claim or contribute to tests
  user        Interacts with ruruku users, e.g. authenticates, adds or deletes users

Flags:
      --config string   config file (default is $HOME/.ruruku.yaml)
  -h, --help            help for ruruku
  -v, --verbose         Sets the log level to debug

Use "ruruku [command] --help" for more information about a command.

Original Otter

This release marks an almost complete rewrite of ruruku. Now ruruku sports a more distributed architecture. There is a single ruruku server which sports a gRPC API used by a web client or CLI. The server and CLI the same binary.

Ruruku now also has a Dockerfile and automated Docker builds: https://hub.docker.com/r/csweichel/ruruku/

Usage:
  ruruku [command]

Available Commands:
  help        Help about any command
  plan        Creates a new testplan
  serve       Starts a ruruku API server
  session     Controls a test session/run
  start       Creates a ruruku API server and starts a session
  test        Claim or contribute to tests

Flags:
      --config string   config file (default is $HOME/.ruruku.yaml)
  -h, --help            help for ruruku
  -v, --verbose         Sets the log level to debug

Use "ruruku [command] --help" for more information about a command.

Bald Shark

This release implements a synchronised data store. Before v0.1.3 the incoming requests caused non-synchronised writes to the session file, which is likely to garble the session file in the progress.

Do not use a release prior to this one.

Know issues:

• cannot restart a session (#33)