Add ability to clone release
We have about 2500 tests at this time. As the process of connecting that many tests, even organized into test sets, is cumbersome (creating another suggestion for that issue), it would extremely helpful to be able to clone a release or iteration to another release or iteration, and carry across the linked items (we only use tests, not sprints or requirements). That way, even though I would have to manually link all the tests to a release, at least for the next release, I could clone and be done, and just add any new tests (or test sets).Speed up linking of tests to configurations
There are only 2 ways to link a test to a configuration...either 1. select the test (or test set), open the link to items, select the configuration folder, and check each sub item (e.g. Windows8>IE, and Chrome and Firefox), repeating for each config folder. 2. select the configuration, open the link to items, specify type and folder, and individually check every item (test) in the folder. Repeat for every configuration. Even with just a few Windows environments, each with 3 or 4 different browsers, times our 2500 tests, and this is a monumental task. While we could have done it as we created tests, our focus was on creating the tests, and not linking..that was a mistake. However now, we need to make these links, yet we are looking at nearly 10,000 clicks/steps. If nothing else, in the selection of tests (or sets) drop down, add a "Select All" to check all tests in that folder. Then we would just need to repeat for each Configuration, each folder...a much more manageable task.
The ability to apply Token files to a Test before running a Test set.
I have a product that requires testing for multiple clients and will use tokenized tests to pass different data (usernames, field names etc). Rather than creating multiple tests that contain the same steps but different token files(1 token file per client) it would bemore efficient for me to have the single test set and select which token file to use. For example, a test that requires all fields on a form to be completed.Client A could have fields 1, 2 and 3 whereas Client B could have fields A, B and C. Each client would have different validation required and/or different character limits. Currently to use the same test I would need to edit the token file and re-upload or make a copy of the test (Which would make it harder keep updated with all the different copies if something changes). I was thinking this process could work in a similar way to attaching configurations/releases to a Test Set. The token files will be attached to thetest set and will be chosen upon running said test set. If anyone has any methods or work arounds for me, it would be great to hear them. Thanks.
