Coming soon
Ostra Code
A model for writing and maintaining test code, in the framework and conventions your suite already uses.
What Ostra Code is for
Writing tests
New specs in the framework you already run, named and structured the way your suite already is.
Maintaining tests
Keeps existing tests current as the app changes, so a renamed selector is not a day of edits.
Your conventions
Follows the page objects, fixtures and naming your suite has, instead of introducing its own.
Grounded in memory
Like the rest of the Ostra family, it reads TestRelic's application memory, which is what is true about your app.
Built for the test code itself
Most of what a test suite costs is not writing a test once. It is keeping the suite right as the product changes: a selector renamed, a flow reordered, a helper moved. Ostra Code is the model for that work on the code.
It is not available yet. Until it is, Ostra Pro writes and fixes tests today, and Ostra Decision tells you which tests a change affects and which selectors are about to break.