Visual Studio IDE

Announcement: This forum has been migrated to provide our customers one convenient and responsive system for all feedback. You can now suggest new ideas, browse and vote on existing ideas in the Visual Studio Developer Community. To learn more about the migration to Visual Studio Developer Community please check out the release blog post.

We’d like your suggestions and ideas to help us continuously improve future releases of Visual Studio, so we’ve partnered with UserVoice, a third-party service, to collect your feedback. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.

This site is for feature suggestions; if you need to file a bug, you can visit our Developer Community website to get started.

Note: your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy and license terms.

We look forward to hearing from you!
- The Visual Studio Team

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Live Unit Testing without Code Coverage

    I like that Live Unit Testing runs my tests as soon as I change my code. I don't like the Code Coverage UI, as I find it too intrusive and not very useful.

    So, I propose that there should be an option to enable Live Unit Testing, without enabling Code Coverage at the same time.

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →
  2. to be able to name test iteration

    It wouldb be nice to be able to "name" test iteration created by many occurrence of parameter.

    The simpliest way, would be to create a first column "Iteration name" and use it in MTM and in web app.

    Thanks

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow to create a new Test Playlist via Mainmenu > Test > Playlist

    In Visual Studio 2015 Pro
    Allow to create a new Test Playlist via the Mainmenu > Test > Playlist

    Now you can only do it in Test Explorer with right mouse click.

    Had to search the interwebs just to find a blog that explains it... -_-

    0 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →
  4. Intersect code coverage results with changesets

    This will make it super easy to identify new code that isn't tested yet.

    0 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →
  5. Test Explorer: Add a mixed mode grouping - e.g. Class + Outcome

    Currently we only have one of the options: Class, Project or Outcome. It would be nice if failed tests are displayed separately like when grouped by Outcome and succeeded tests are grouped by the selected option: Class, Project... etc.

    0 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →
  6. Find all tests for a class or function

    I would like to have the option to right click on a class or function and get the option "Select all related tests". Then in Test Explorer I should get a new group "Selected Tests" where all the tests are listed which somehow execute that function, or all the function of a class, if a class was right clicked.

    0 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →
  7. Display recently run tests on top of test list

    Display recently run tests on top of test list
    Maintain selected test (and ensure scrollbar is on such position that the selected test is visible) when changing or clearing Search field.

    0 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →
  8. show unit test results in solution view

    I find it annoying to constantly switch back and forth between the Test Explorer and the Solution Explorer. It would be much more efficient if the solution explorer showed the test results.

    After a test run, you could have a green check mark or a red x beside the class that contains the passing or failing tests.

    it would also be nice if you could "open up" a test class to see the test functions in the solution explorer. That way I could open up the test class I am working in, run the tests and I would see a…

    0 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →
  9. show unit test results in the test function

    Take a look at how xcode on the mac reports unit test assert failures. it shows the failure in the editor window for the test function.

    By putting the error right near the code that had the error, it makes it much easier to determine that a test failed and where it failed. I find it very cumbersome to have to go over to the test explorer, and click on a failing test, then click on a link in the summary window just to figure out which line of the test failed. And then I find it very difficult to…

    0 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →
  10. run tests should queue if it isn't available

    For some reason in my instance of the IDE and project, VS takes a good 30seconds to a minute after the tests are complete or after it tells me there was a compile error before it will let me run the tests again. And during this time, Ctrl-r, Ctrl-t is unavailable.

    It would be much nicer if run tests command was still available and if it can't run the tests immediately, it puts the command on a queue that will get run as soon as whatever is happening finishes. (I have no idea what VS is doing for 30 s…

    0 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →
1 2 17 18 19 21 Next →

Feedback and Knowledge Base