Ruby Raider

Files and settings

The Files tab shows every file in your project and holds the settings your test runs use: the address, the browser, timeouts and more. Changes to a setting take effect on the next run.

The file tree

The left side lists the project's folders and files. Click a file to open it in the editor on the right. Right-click a file for Copy path, Rename, Duplicate and Delete.

The run button on the project's row, at the top of the tree, runs every test in the project; see Running tests and results.

A dot before a file's name means it has changes you have not saved.

The editor

The editor works like a code editor: it colours the code and has the usual editing keys. Click Save above it, or press ⌘S (Ctrl+S), to save. The status next to Save reads "Unsaved changes" until you do. See Saving your work.

Toolbar settings

The toolbar above the tree sets how tests run in this project.

"Saved" shows briefly when a setting is stored.

More options

Click More options on the toolbar for:

Saved logins

Tests that use a saved login log in once and keep the login for later runs. The Dashboard lists each saved login, how old it is, and whether it has expired. Click Forget to delete one; the next run logs in again.

Paths

Where new pages, specs and helpers are created is set under Paths on the Scaffolding tab; see Scaffolding.

Terminal

Click Open terminal, next to the tabs on the Files tab, to run commands in the project's folder without leaving the app. You can run any raider command there; see Scaffolding.