Test Manager Improvements

[steven.boxhall]

Some suggested improvements if you want Test Manager to be considered a serious Test Management tool:

Requirements - Map the template to match widely used project management tools in the market, such as Jira, Azure DevOps, so that it has the basic information:

• Acceptance Criteria, Story Points/Estimate, Priority, Owner, Sprint, Area, Value, State

Test Cases - Consider re-work of the test steps, not very user friendly with the large box per step, meaning constant scrolling up and down the page to see the steps. Use the full width of the page for action and expected result.
Consider whether teams can select BDD template for test cases or standard template
Most tools allow you to share tests from other test cases - enhance the tool to allow you to import tests from another test in the tool

Test Sets - When creating a test set, I would expect to create the test set name and then add the tests to the test set. At present, you just create the test set, then have to navigate through a few steps to then add tests. This seems very un-user friendly.

No option to Clone the test set - sometimes you have to re-run an entire test set for multiple runs, would be good to clone rather than re-create each time.

Overall - it would be good for each are to be able to create a folder structure as well, so that you can keep requirements, tests, test sets all kept tidy. Without this at the moment there is just a long list in each area. This makes it hard to find what you want. For example a project may be broken down by system, so you can break the requirements down by the system and have individuals working on those systems in specific folders. The same with the test cases.

It would be good to see some more work on the integration with Azure and Jira as well, to really make it worth using Test Manager over these tools and being able to promote the use of the tool rather than directly using Azure or Jira. If there was full 2-way integration, it would really help promote this.