Rima AI settings, explained with examples

What Rima AI does

You describe a test in plain words, the way you would explain it to a new team member. For example: "Sign in as a parent, book a maths lesson for next Monday, and check that the booking shows on the dashboard."

Then Rima does the work:

1. It opens your site in a real browser.
2. It clicks through your pages and writes the steps.
3. It runs the whole test, from start to finish, to check that it passes.
4. It shows you the test. You read it, and you save it if it looks right.

Rima tries things on your real site while it works. So before a step that cannot be undone, like paying or deleting something, it asks you first.

You find the settings in your project settings, in the section called Rima AI. You set them once, and Rima uses them for every test it writes in that project.

Notes for Rima

This is a free text box. Rima reads it first, before every test it writes. Use it to tell Rima anything special about your site that it cannot guess from the page.

Good things to write here:

• Rules that are not clear from the page, like an approval step.
• Words your site uses in its own way.
• Where things are, if they are hard to find.

Keep it short and true. One clear sentence per rule works best.

Test data: fresh accounts or your test account

Most tests need someone signed in. This setting decides whose account Rima uses. There are two choices.

Make fresh accounts when the site allows it

This is the default. Every time the test runs, Rima signs up a brand new account and uses it. It signs up with a random email address from its own inbox, so it can read the verification email and finish the sign-up by itself.

Before Rima builds a test this way, it first checks that a new account can really reach the page you want to test. If it cannot, Rima will not pretend it can.

Why this is good:

• Your real test account stays clean. No leftover orders or bookings pile up in it.
• The test can run every day, because each run starts from a new account.

Rima may save the sign-up steps as their own small test, which runs first. Then other tests can reuse it.

Always use my test account

Rima signs in with the test accounts you add below. Pick this when a fresh account will not work, for example:

• New accounts need approval. On the tutoring site, an admin must approve every new tutor.
• A captcha blocks sign-up.
• The test needs data the account already has. On the delivery app, a test that checks a client's order history needs a client with past orders.

Test accounts

Add one test account for each kind of user on your site. Rima then signs in as the right user for each test. For each account you fill in:

• Kind of user: a name like Tutor, Parent or Child.
• Signs in with: email, username or phone number.
• The sign-in ID and the password: you pick the project variables that hold them, like TutorEmail and TutorPassword.
• Test that signs in as this user (optional): a saved test that signs in as this user, like "Login as tutor".

Run first, by default

These are tests that are ticked for you each time you open Rima to write a new test. You can pick up to 5. The most common choice is a sign-in test, like "Login as tutor".

"Run first" means these tests play first, in the same browser. The new test then carries on from where they stopped. "Login as tutor" ends with the tutor signed in, so the new test starts signed in too.

When you press Play on the saved test later, the same list runs first. Rima checks the test the same way, so its check matches what happens in real runs.

Saving values

Sometimes a test needs to remember something from one page and use it on a later page. Rima can save it in a variable. There are two boxes here.

Rima may save values into new variables

This is on by default. Rima can make a new variable when a test needs one.

Rima may change variables that already exist

This is off by default, and we suggest you leave it off. Then Rima never replaces a value you already set up, like the email and password of your test account.

Steps that cannot be undone

Some buttons do something real that you cannot take back. For example: Pay now, Place order, Delete account or Cancel subscription. Rima tries the test on your real site while it writes it, so clicking one of these really happens.

You choose what Rima does with these steps:

• Ask me before running them (the default): Rima stops and asks you. You say yes or no each time.
• Never run them while writing a test: Rima keeps the step in the test, but does not click it while it writes the test.
• Always run them: Rima runs every step without asking. Only use this for a site made for testing, where no real money or real data is involved.

What "Checked in part" means

If Rima does not run one of these steps, it still checks every step before it. That step, and the steps after it, are not run. The test then shows Checked in part, so you know which part was not tried.

Before showing a test

With Run the whole test first, checks included turned on (the default), Rima plays the full test before you see it. It runs it the same way Play will. So you only see tests that pass.

But Rima does not hide real bugs. If your site itself is broken, Rima keeps the check and tells you. It will not remove a check just to make the test pass.

Start in: plan first or build it directly

• Plan first (the default): Rima shows you the steps in plain English first. You read them and change anything you want. Rima then runs the test again with your changes. Nothing is saved until you say so.
• Build it directly: Rima builds and checks the test straight away, and then shows it to you.

Plan first is a good choice while you get to know Rima. You can also switch between the two in the Rima window for a single test.

Tests that only work once

Some things on a site only happen once for each account. For example:

• A welcome tour that shows only the first time a user signs in.
• A coupon that can only be used once.
• Deleting data. Once a lesson is deleted, it is not there for the next run.

A test like this passes the first time and fails the second time. Nothing is broken. The thing already happened.

Rima keeps tests repeatable in two ways:

• A fresh account each run. A brand new parent sees the welcome tour every time.
• Create, then delete, in the same test. The test adds a lesson and then deletes that same lesson. The next run has a lesson to delete again.

Quick setup for a new project

1. Write a few Notes for Rima about the rules of your site.
2. Pick your Test data: fresh accounts if anyone can sign up, your test account if not.
3. Add a test account for each kind of user, with the variables for the sign-in ID and password.
4. Add your sign-in test to Run first, by default.
5. Leave "Rima may change variables that already exist" off.
6. Keep Steps that cannot be undone on "Ask me before running them", unless this is a site made for testing.
7. Keep Run the whole test first on.
8. Start in Plan first while you learn how Rima works.
9. Press Save.

That is it. Now describe your first test in plain words and let Rima write it. If something is not clear, contact us and we will help.