Octomind goes CLI and other news
The summer that keeps on giving: You now interact with Octomind via their CLI now. You can create, execute, and run tests, debug test cases locally, launch the private location worker and generate tests in batches. You can use teardown to isolate your tests - we added teardown functionality to the steps editor. Teardown allows you to configure a test that cleans up artifacts created during test...
Prompt without (over)engineering it! July Feature Drop // Part 2
You never signed up to be a prompt engineer - and now you don’t have to. We’ve tuned the Agent to clean up and enrich whatever natural-language prompt you give it. The Agent expanded that prompt into a structured prompt with three clear sections: Test INTENT – a description of the user journey INSTRUCTIONS – the concrete interactions (steps) to perform EXPECTED OUTCOME – the final state, ready...
Tell agent to get stuff done - July Feature Drop // Part I.
Converse with the Agent to direct Octomind! This goes far beyond a glorified AI docs search. Via MCP, we enabled our agent to launch generation workflows, create items, change settings, query and execute tasks directly from the chat window. All the things you might need too much time to figure out and do “manually” in Octomind app. Agent, create these tests and run them Agent! set up a new...
It's a recorder, but better
Octomind was, is and will always be AI-first. AI is THE technology to enable a substantial increase in testing productivity. What we learned in the process of building it is how people interact with AI - where its assistance is the most useful and where you need to plug in a human to propel the Agent in the right direction. This informed the philosophy behind our new test recorder feature. We...
We made test maintenance faster. By a lot.
you might have noticed over the past few weeks, that out test reports look differently. Failed tests are clustered, test run details is packed with more information and new buttons appeared leading to new features. Let me explain. From the start we knew that after test generation and execution, we would have to tackle test maintenance next. It's the reason why many teams decide to stay away...
