​
Sign up to Octomind in under 2 minutes

​
1. Give us a URL

We’ll ask for a URL of the application you want to test. The URL has to be publicly accessible. We can test both in staging and in production, as long as we can access the site.
enter your url screen

First page of the setup flow - link to your website, screenshot 10/2024

​
2. Name your project

The second page will render a screenshot of the url you provided. We check if it is accessible. You can name your project now. We’ll propose one similar to the url you provided. But you can choose your own.
name your project screen, screenshot 07/2024

Second page of the setup flow: Name your project, screenshot 07/2024

​
3. Sign up

Now we need to sign you up. Please, give us your email, so we can get in touch.
create account, screenshot 10/2024

Third page of the setup flow - create account, screenshot 10/2024

You should receive a confirmation email that contains a link for you confirm your email and set your password.

​
4. Open the Octomind app for the first time

After being redirected back to app.octomind.dev, you will land on your project overview page. Create a new test section is highlighted - that’s the place to start.
Opening the Octomind app on project overview for the first time

Project overview page after sign-up, 07/2025

​
5. Create your first tests

Click on the get started button. A selection of recommended tests will appear.
Recommended tests section when creating first tests

Recommended tests section, 07/2025

Our AI Agent has gone through your website, checked what relevant test cases you might want to create first. Select one or refresh to get new recommendations. Click next. If the AI Agent finds a required login, it will ask you for test credentials. It will use them to generate and run a login test. It will be added as dependency for other tests. So will be the cookie banner test if one is found.
Required login test identified and recommended

Required login test identified and recommended, 07/2025

These credentials are only usable for username/password logins not for social logins. Login using your Google, Facebook, etc. account will not work.
You can create a login test later. Learn how to create a pre-prompted login test.

​
6. Refine the prompt

We will generate test cases you selected. But first, we need you to review the prompt we prepared. You can instruct the Agent in natural language to change the prompt here, or refine the prompt manually in the next step.
Refine prompt example

Refine prompt example, 07/2025

Click generate to add details, rename the test or refine the prompt. When everything is all set, click finalize.
Finalize test case

Finalize test case, 07/2025

Watch a short video where we showcase these steps on a sandbox app.

​
7. We generate the test case

We started generating your test case.
test case in the process of being generated

Test is being generated, 07/2025

If you notice the Agent went off track, you can take over the generation process, record your specific few step manually and handover back to the Agent. Watch how: It’s possible that the Agent fails to generate a test (here are some reasons why) or needs help with something - the test is highlighted in yellow. This is a step by step guide on how you’ll help the Agent by nudging it in the right direction. After being generated successfully, in the right panel, proceed to validation to run it and check whether it’s working properly.
Validate a generated test case

validate a generated test case, 07/2025

Create more tests using our recommendations, spawn existing tests or prompt new tests from scratch.

​
8. Run tests to check your app for bugs

Once you’ve built your test suite, you can execute your active test cases to check your app for bugs. Every test execution will produce a test report with details of the run and debugging information in case of a failed test.

​
9. Evaluate your test results

Inside each test report, you can find the test results for the executed test cases:
  • a green test result indicates a successful test run, meaning that your site passed the test described in the test case
  • a red test result indicates a test failure, meaning we could not successfully run the test case steps. These are the possible reasons for failed test.
Click on it to see in which step is broken and diagnose the reason for the failure. If it’s fixable, you can debug it. Find out more about test reports.
Example of a Octomind test report

Example of a Octomind test report, 05/2025