Feature Requests

It would be awesome if I could mark some steps to create one shared step out of those. Currently only one single step can be transformed to a shared step.

Shared step is one of critical thing while creating tests but there are few things which should be must have in shared steps: passing variables in the shared steps so that we can have dynamic shared step instead of static shared step. ability to group some shared steps in folders. Having folder structure will help in organizing the shared steps. This is useful when we have many shared steps Importing & exporting shared steps from one project to another. Having child steps in shared step Ability to view test cases linked with the shared step

Is is possible to add a modal window within the Test Case Edit page where a shared step can be edited on the go without having to navigate to the Shared Steps page? A client can choose to save changes for just this test case or for all shared steps from this modal window

I want see the exact cases numbers (with links?), not just the total number

The option to GROUP shared steps (by folders or tags) will allow to classify and easily manage many steps. Use case: we are going to create approx. 600 shared steps and need to classify them in order to understand to which module of our system they relate. Thanks in advance!

I would like to clone shared steps in the Shared Steps section to reduce time writing similar steps with a little variation.

Currently, it seems like shared steps can only be deleted 1 by 1. It would be really helpful, to be able to select multiple shared steps to delete, be able to choose "convert" or "delete" , and do a batch update for all of the shared steps selected. Or while selecting the shared step give option to select the steps.

Is it possible to implement nested Shared steps? I mean to create new shared steps which would include already existing shared steps. F.i. For login functionality we should have at least 3 separate steps - input email, input password, click submit. But for testing functionality based on if user is logged in we don't need such atomic steps. Instead we can create step Login which can include all steps above

It would be very useful to share the shared steps between projects, because different projects can indeed have similar modules and, accordingly, similar steps.

Unless you provide an extremely long and descriptive title to your Shared Step, it can be hard to remember what the original intent of the Shared Step was. Providing a Description field to Shared Steps allows for concise naming and better organization without losing context.