We are using cookies for secure log-in and to improve our app.
First party only, no data krakens 🦑 Learn more in our privacy policy.
Testing workflows vary dramatically between testers and coders. QA experts need intuitive interfaces for rapid test creation, while developers demand programmatic control and integration with their existing toolchain.
We have just shipped a big upgrade for the latter group. Software engineers can now interact with Octomind via their CLI. They can create, execute, and run tests, debug test cases locally, launch the private location worker and generate tests in batches.
We will continue improving our web user interface to intuitively serve a broad spectrum of users while expanding options for peeps who want to stick to their tools and workflows. Whether it’s MCP, API or CLI access.
.gif)
How to install and use Octomind CLI
Clean up after your tests automatically
To enable more test isolation, we added teardown functionality to the steps editor. Teardown allows you to configure a test that cleans up artifacts created during test execution automatically. You can set it up using the app’s interface or programmatically via a javascript step.
Compare test runs faster thanks to the upgraded splitscreen
.webp)
.webp)
An UI and convenience tweak - we’ve reworked test debugging views to make you even faster at identifying why a test broke and how to fix it. To compare the failed run with the last successful one, just click the splitscreen icon and the timeline of the most recent passed test run expands into view.
++ use the `sync` button to point to the same moment in the run timeline
++ resize the view to your liking
++ use the filter menu on the right timeline to see how good a test performs over time
.jpg)
As its engineering teams embraced AI-driven development, Deriv - one of the world’s largest online brokers - recognised the need to modernise its QA processes to keep pace. Deriv deployed Octomind to reduce test maintenance, aid non-technical team members with automation, and build a scalable, resilient QA framework to align with modern development cycles.
Why developers need AI-powered e2e test automation
We feel strong about developers doing e2e tests. To quote Daniel Draper, our lead octoneer:
“Tests are a discussion point at every company I ever worked at. And I feel the *ONLY* way to have them bring value is if they run in your pipeline during development already. This is true for unit tests (obviously), but should be true JUST as much for your e2e tests.
I also think that if you take good care of your test suite and build them so they run fast and reliably, most devs WILL get on board and maybe even love them. As I have proven even for people who were maybe less on-board with tests in the first place, but I convinced them eventually, with hard work, sweat and tears. “
So I've summarized 6 reasons why devs should add e2e tests to their CI pipeline in a new blog.
---
I know, this was a longer one. Let me know if you prefer snappier updates more often. We don’t want you to miss any new tweaks.
