As I understood the test steps are just represented by one text field and have to be documented sequentially. It would be better to realize the test steps (with the expected results) in an extra table related (with a relationship) to the respective test case.
The test step should have the following attributes at least:
Hi Torsten and welcome to the Testiny forum!
You are right, with the “Steps” template all steps are represented in a single text field in the test case when transmitted via the API, structured as a document. This is for simplicity of the API, both for use in the Testiny frontend, but also for end user API usage.
The document in which the steps are structured is open for extension, though, and basically already has “action” and “expected results” as columns and could be extended to contain a “data” column, too.
Also the option to link common/shared test steps will be possible.
Both shared steps and better data mapping is already on our roadmap, so I take your suggestion as an upvote on these topics. Thanks!
Best regards,
Alex