diff --git a/edit-test-case.mdx b/edit-test-case.mdx index 9d6c8d0..6b48ffa 100644 --- a/edit-test-case.mdx +++ b/edit-test-case.mdx @@ -72,7 +72,7 @@ Octomind test steps can be flexibly manipulated. You can **drag and drop** steps You can edit the prompt and have the AI agent `regenerate` test steps based on the new prompt. We will ask you to select **the last step** in the sequence you want to keep. The AI agent will regenerate test steps from this step onwards. -Or you have simply hit the `regenerate` button to rediscover the steps based on the same prompt. +Or you have simply hit the `regenerate` button to regenerate the steps based on the same prompt. + First active test cases AI auto-generated - screenshot 07/2024 {" "} - Currently, only one instance of the worker is supported. We will support - multiple instances of the worker with the same name as we scale. + Currently, only one instance of the worker is supported. We will support multiple + instances of the worker with the same name as we scale. ## Run diff --git a/proxy/private-location.mdx b/proxy/private-location.mdx index e7f2aa7..a1c3fc9 100644 --- a/proxy/private-location.mdx +++ b/proxy/private-location.mdx @@ -25,9 +25,9 @@ It requires access permission to specific public IPs: `35.192.162.70` or `34.159 The embedded Squid proxy server allows requests from the private network, mimicking public proxy requests from within the customer’s network. -### Test execution and discovery +### Test execution and generation -After registering the worker with Octomind, users can configure the proxy location for executing discovery or test runs. +After registering the worker with Octomind, users can configure the proxy location for executing generation or test runs. ## Usage @@ -50,8 +50,8 @@ be unique for your organization. {" "} - Currently, only one instance of the worker is supported. We will support - multiple instances of the worker with the same name as we scale. + Currently, only one instance of the worker is supported. We will support multiple + instances of the worker with the same name as we scale. ## Run diff --git a/proxy/proxy-settings.mdx b/proxy/proxy-settings.mdx index 2071646..ca6cee3 100644 --- a/proxy/proxy-settings.mdx +++ b/proxy/proxy-settings.mdx @@ -6,8 +6,8 @@ icon: "server" ## Overview -In project settings you can control from which location your website is being discovered and also -from where your test will be runned. +In the project settings you can control from which location your website is being accessed and also +from where your test will be ran. proxy settings diff --git a/rate-limiting.mdx b/rate-limiting.mdx index de00443..2d27466 100644 --- a/rate-limiting.mdx +++ b/rate-limiting.mdx @@ -4,14 +4,14 @@ description: "What is rate limiting and how to deal with it" icon: "gauge-max" --- -Whenever the AI agent discovers user flows on your page, or when the test runner executes the tests - we are sending requests to your application. +Whenever the AI agent generates tests for user flows on your page, or when the test runner executes the tests - we are sending requests to your application. To ensure a well defined behavior all requests are sent through **two fixed IP addresses** - `35.192.162.70` and `34.159.153.198` (europe proxy). -## AI agent discovery +## AI generation -AI agent discovers user flows on your site in a similar way a human would use your web application. However, most of the time the agent interacts with the website slightly faster than a human would. -Also, more discoveries might run in parallel. +AI agent generates test cases based on user flows on your site in a similar way a human would use your web application. However, most of the time the agent interacts with the website slightly faster than a human would. +Also, test case generation can be run in parallel. ## Test runner @@ -20,7 +20,7 @@ This can lead to either an overload of your application or a rate limiter gettin ## Login / Authentication -If your application requires a login, the configured test user is used for the AI agent discovery as well as for the test runs. This could also lead to **hitting a limit of allowed logins**, depending on your login system. +If your application requires a login, the configured test user is used for the AI test case auto-generation as well as for the test runs. This could also lead to **hitting a limit of allowed logins**, depending on your login system. If you are using a 3rd party login service, there are most likely security configurations in place that prevent users from logging in too frequently. ### OTP / 2FA @@ -29,5 +29,5 @@ While Octomind supports a login with a **one time password (OTP)**, it might run ## Rate limiter -If your application is protected against [DoS Attacks](https://en.wikipedia.org/wiki/Denial-of-service_attack) with a [rate limiter](https://en.wikipedia.org/wiki/Rate_limiting) it is very likely that Octomind test runs and/or AI discoveries will fail. +If your application is protected against [DoS Attacks](https://en.wikipedia.org/wiki/Denial-of-service_attack) with a [rate limiter](https://en.wikipedia.org/wiki/Rate_limiting) it is very likely that Octomind test runs and/or AI generation will fail. The easiest solutions is to configure and exception for our IP address: `35.192.162.70` and `34.159.153.198` (europe proxy) for white listing. diff --git a/test-case-creation-strategy.mdx b/test-case-creation-strategy.mdx index c257060..e83f6f7 100644 --- a/test-case-creation-strategy.mdx +++ b/test-case-creation-strategy.mdx @@ -22,10 +22,10 @@ You can have the AI agent generate more test cases. Go into the test case and ho The AI agent will auto-generate up to 3 new tests based on the one you started it from. The original test will be added as **dependency**. We will auto-generate steps for every found test case and validate them. - + have AI suggest more test cases