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

Provide a way of exporting or converting webtestresult files to text

Understanding web test results and finding dynamic data is hard work. The search facilities within Visual Studio 2012 are primitive when looking at web test results. There are no options for annotating a result file to remind oneself of what has been found and can be ignored, found and may be relevant etc.

It would be nice to have a textual form of the whole of the web test result file that can be examined with ones favourite text editor and where annotations etc can easily be added.

Possibly the output should be XML to allow easy recognition of the different parts of the output.

8 votes
Sign in
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    AdrianHHH 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.


    Comments are closed
    • AdrianHHH commented  ·   ·  Flag as inappropriate

      It would also be very useful to have a way of exporting the web test results from load tests. It would be useful to have a way of exporting all test logs and, possibly, only selected test logs from a load test.

      Analysing multiple load test failures is time consuming. Currently you can click on a "test log" entry in the "error" table to view the log within Visual Studio. If one test has multiple errors then each error gets a "test log" entry with no way of seeing which errors are for the same test run and so in the same log file. So examining all the log files of a load test requires lots of clicking of "test log" links many of which refer to files that have already been opened.

    Feedback and Knowledge Base