Ruby Raider

Saving your work

Raider Desktop saves in two ways. Recorded tests save themselves. Files you edit in an editor need Save. This page explains which is which, and how the app shows you that something is not saved yet.

What saves itself

A recorded test, after Stop & save. While you record, the steps are not in your project yet. Pressing Stop & save, or ⌘⇧R (Ctrl+Shift+R), writes them to the project as a test.

Every change to a saved test. Once a test is saved, moving, editing or deleting a step saves straight away. Under the step list, the app reminds you: "Changes to this test are saved automatically." You never need Save on a recorded test, and pressing ⌘S (Ctrl+S) there does nothing because there is nothing to save.

If you press ⌘S (Ctrl+S) while recording, it does the same as Stop & save.

What needs Save

Files you open in an editor are only saved when you ask:

To save, click Save above the editor, or press ⌘S (Ctrl+S). File › Save in the menu does the same.

How you can tell something is not saved

While an editor has changes you have not saved:

The window title also shows as unsaved while you are recording, and while a new test has steps that Stop & save has not written yet. Those are the moments your steps are not in the project.

When you leave with unsaved changes

If you open another file, switch tabs, or close the window while an editor has unsaved changes, the app asks: "Save changes to file name?"

If you close the window during a recording, Raider saves the recording first.