I’m used to building my testcases like building blocks and set them together in a testset. This way I can have just one place to update a testcase if there is a change in the app I’m testing. I find it better when i comes to maintenance.
any hints and tips, on how this can be done, are very much welcome.
Hi and welcome to the Testiny forum!
I thought that this is more a question to the community. Anyway, since we also use Testiny ourselves, I’d like to share some approaches:
- for test cases in the same area and sharing prerequisites, we use the test case folder description for these common instructions
- for test cases requiring the same initial steps but in different areas, we use a common “prerequisite” test case that we link to
Best regards,
Alex
Testiny does not have a separate feature for creating test sets. Instead, you manage your test cases using folders, where you can group them in a structured way based on features or modules. When you need to run tests, you create a test plan that selects the required test cases, and then you execute them through a test run. In this way, folders handle organization, test plans define what to include, and test runs are used for execution, which together replace the need for traditional test sets.