How can we improve Visual Studio Team Services (VSTS)?

A way to identify what an test case iteration is testing allowing the test case steps to be generic.

A feature that allows testers to describe what an individual test case iteration is testing. Right now I add a paratemeter to the last steps expected results "@Notes" and for each iteration of a test case I add to the Notes what I am testing in each iteration. Example would be testing a address site. My test case will go through all the address fields so any testing I would need can be done with parameters and iterations even boundary. But I need a easy way to identifiy what is being tested by an iteration.

10 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Debra Lloyd-ForsythDebra Lloyd-Forsyth shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    We want to build a product that our users love. User Voice provides us a great platform to let any TFS/VSTS user tell us what is important to them. We closely pay attention to the most popular suggestions.

    Too many suggestions in User Voice however will make it hard for you to find the suggestions you want to support. We will regularly archive the suggestions created more than a year ago and has low number of supporters.

    When a suggestion is archived, you can still view them, but you can’t support them anymore. Also Microsoft will not pay attention to these suggestions.

    2 comments

    Comments are closed

    Feedback and Knowledge Base