diff --git a/changelog.mdx b/changelog.mdx index e0103fa3..9268bcf7 100644 --- a/changelog.mdx +++ b/changelog.mdx @@ -4,6 +4,33 @@ description: "All the nice stuff you asked for" icon: "sparkles" --- +## 2024-04-15 + +- `scheduling test reports`: We are now enabling you run your test reports on a fixed schedule (daily/ weekly/ bi-weekly). There's even email notifications now for when your scheduled run failed so you never miss a ~beat~ bug. + + scheduling of test reports + + +## 2024-04-08 + +- `snapshots for picking locators`: Not familiar with selectors and DOM elements? We got you covered! Test case steps now allow you to select elements in your page visually, both for interacting with them and asserting that they are there. + + + picking elements inside of page snapshots + + +- `reworked publish workflow`: whenever you save a draft of a test case, you get the option to publish it to include it in future test report runs + +## 2024-04-02 + +- `expandable step editing`: the panel for editing test case steps now expands and gives you more space to make changes to your test cases + ## 2024-02-23 - `improved stability`: made sure our app is running smoothly without hick-ups even with multiple test report running in parallel. Now our agent and test execution are serverless. diff --git a/execution-without-ci.mdx b/execution-without-ci.mdx index 55ab0c7e..011bb1f3 100644 --- a/execution-without-ci.mdx +++ b/execution-without-ci.mdx @@ -1,10 +1,10 @@ --- -title: Execution without CI -description: "Trigger Octomind execution of test cases manually" +title: Programmatic execution without CI +description: "Trigger Octomind execution from outside our app" icon: "person-digging" --- -If you don't have pipelines or you just want to manually trigger the test execution, you can do it with a cURL command. +If you don't have pipelines and want to manually trigger the test execution from outside our app, you can do it with a cURL command. You can retrieve it conviniently with prefilled parameters from within the app by selecting `in app via terminal` from the `generate report` button on the overview page: diff --git a/images/changelog/schedule.gif b/images/changelog/schedule.gif new file mode 100644 index 00000000..e1e421a5 Binary files /dev/null and b/images/changelog/schedule.gif differ diff --git a/images/changelog/snapshots.gif b/images/changelog/snapshots.gif new file mode 100644 index 00000000..ec8bfc05 Binary files /dev/null and b/images/changelog/snapshots.gif differ diff --git a/images/scheduled-report-email.png b/images/scheduled-report-email.png new file mode 100644 index 00000000..022aed99 Binary files /dev/null and b/images/scheduled-report-email.png differ diff --git a/mint.json b/mint.json index acda6602..f6d0f4e7 100644 --- a/mint.json +++ b/mint.json @@ -73,6 +73,7 @@ "test-reports", "debugtopus", "integrations-overview", + "scheduled-execution", "execution-without-ci", "under-the-hood", "octo-dictionary" diff --git a/scheduled-execution.mdx b/scheduled-execution.mdx new file mode 100644 index 00000000..1ad3f1de --- /dev/null +++ b/scheduled-execution.mdx @@ -0,0 +1,25 @@ +--- +title: Scheduling test report runs +description: "Run your test reports in regular intervals" +icon: "clock" +--- + +If you don't have pipelines but nevertheless want to run your test reports on a regular schedule, you can do that via our scheduling feature in the test report section of the project overview page. + +There, you can pick between the following run intervals: + +- daily +- weekly +- bi-weekly + + + scheduling of test reports + + +## Email notifications + +We will inform you via email in case a scheduled test report fails. You can always opt out of these notifications in our in-app settings. + + + email notifications + diff --git a/test-reports.mdx b/test-reports.mdx index 237bece7..f119cb66 100644 --- a/test-reports.mdx +++ b/test-reports.mdx @@ -17,6 +17,14 @@ You can also reach the test reports via the sidebar. /> +## Scheduled test reports + +If you want to [run your test reports on a fixed schedule](/scheduled-execution) , the test report section of the front page gives you the option to decide on a daily/ weekly or bi-weekly interval. This allows you to ensure that your app continues to work flawlessly over time. + + + scheduling of test reports + + ## Test report in your CI/CD pipeline Once tests are executed, and you have integrated octomind into your [CI/CD pipeline](/integrations-overview) you can receive a comment in your pull request which looks like the example below.