Visual Studio

Welcome to the Visual Studio UserVoice site. Let us know what you would like to see in future versions of the Visual Studio suite of products. This site is for suggestions and ideas. If you need to file a bug, visit the Visual Studio Connect site: https://connect.microsoft.com/visualstudio.

Enhance Coded UI Test to include the many common features found in commercial-off-the-shelf software test automation packages like SmartBear's Test Complete. These packages typically feature very rich functionality in mapping and managing UI control objects, whereas Coded UI does not. Packages like Test Complete also boast an impressive list of technologies with which it is compatible. Coded UI is limited in this respect as well.

I need to run test inside MTM, and I need to add a TestSettings configuration to configure some options, but I need to disable deplyment as I need to run test in the build location.
Using visual studio testsettings there is a check in the deplyment section to disable deployment, but inside MTM testsettings options there is no such option, there is only the possibility to add folders, not to disable deplyment

For MTM scenarios, you would need to import action recordings from MTM into a Coded UI Test and change browser type to the desired one.

I would like to know if this satisfies the needs of folks on this thread and I can close this to release votes or if people are specifically looking for the ability to specify browser type from within MTM.

With the MTM 2012, it is possible to change the order of test cases within one test suite and this order is considered when testing. This functionality is missing in the web environment. It is not possible to order test cases and then have somebody else test them in a specific order. If a test suite is run, the tests are ordered by ID only. Make this work for both manual & automated tests.

A significant portion of MTM has moved to the web, however the MTM client still has to be used for rich bug creation, rich action recordings, and rich test run data collection, however the User Experience of MTM is stuck in 2009 and is woefully out of date.

I'd like to have a complete UI overhaul of the MTM client with an improved Modern UI.

I'd like to be able to have excel embedded in the client so as to be able to bulk update test cases, test suites, and test plans.

Give testers a modern MTM client for 2015 and don't leave us with a tool that looks like it came out of .Net 3.0 from 2009.

A significant portion of MTM has moved to the web, however the MTM client still has to be used for rich bug creation, rich action recordings, and rich test run data collection, however the User Experience of MTM is stuck in 2009 and is woefully out of date.

I'd like to have a complete UI overhaul of the MTM client with an improved Modern UI.

I'd like to be able to have excel embedded in the client so as to be able to bulk update test cases, test suites, and test plans.

Include Microsoft Fakes with all editions of Visual Studio including Professional edition rather than being restricted to developers with Ultimate or premium editions of Visual Studio. This will allow all Visual Studio developers to leverage the capabilities of the Fakes mocking library since mocking/stubbing is a necessary part of every developer's Unit Testing toolbelt.

I don't think it is acceptable to restrict and prevent developers from adopting good software practices. Today we preach TDD is or should be mandatory for good quality code, in VS2010 we get Pex and Moles delivered into the hands of many programmers and with VS2012, this is taken away, shifted out of reach AGAIN.

Whilst it might be a slight compromise to provide fakes with the premium edition, it is not what we need to build TDD in to create professional developers. Visual Studio is an exceptionally powerful tool for developing on the microsoft platforms which drive MS revenues and to demonstrate its power and take that power out and hold it out of reach of developers committed to the Microsoft eco system seems incredibly short sighted.

MS say that the Visual Studio team is a profit making entity and has to make profit. When are the revenue teams going to calculate the ROI to the rest of the MS business teams by creating more skilled MS platform developers? MS is transitioning to Azure which will become more a dominant platform if we can easily create high quality software to run on it.

Include Microsoft Fakes with all editions of Visual Studio including Professional edition rather than being restricted to developers with Ultimate or premium editions of Visual Studio. This will allow all Visual Studio developers to leverage the capabilities of the Fakes mocking library since mocking/stubbing is a necessary part of every developer's Unit Testing toolbelt.

I don't think it is acceptable to restrict and prevent developers from adopting good software practices. Today we preach TDD is or should be mandatory for good quality code, in VS2010 we get Pex and Moles delivered into the hands of many programmers and with VS2012,…

I found in VS 11 Beta or VS 2012 RC, when I did some unit test, there is no trx file that stores test results any longer in the TestResults folder, so in this case, I have no way to check my previous test results, this is very inconvenience, especial when I want to save all my unit test results in somewhere, why did you remove this feature in the new version?

I have to assume the people who developed the VS2012/2013 test explorer view never actually had to use it in production. The test explorer view is horribly limited in comparison to the one in VS2010.

1. Running tests does not open the Test Explorer window until after all the tests completed running. There's literally no indication that anything is happening. VS2010 immediately opened the window to show you that the tests were running.

2. Where are the columns? Most importantly: the error message column. if I'm dealing with multiple test failures, I almost always just need to see the error messages at a glance. Having to select each individual test just to see the result is annoying.

3. Where'd the ability to run tests in context go? There's no way to run an individual test without going into the full test list, finding it, and then selecting it just to run it. This might be okay if you have a project with 10 tests, but a solution with thousands of tests makes this arduous. This needs to be fixed badly. Either bring back the "run tests in context" button or at least add some right click menus for "Run this test" and "Run all tests in class".

4. The progress bar is terrible. A five pixel high bar might be useful to someone with an 800x600 monitor, but for the rest of us a barely noticable progress bar is not enough to know that all the tests finished passing. ****, half the time the progress bar color doesn't even change. It just stays red/orange rather than changing to green.

Please fix this. It has made working with unit tests far more of a chore than it needs to be.

I have to assume the people who developed the VS2012/2013 test explorer view never actually had to use it in production. The test explorer view is horribly limited in comparison to the one in VS2010.

1. Running tests does not open the Test Explorer window until after all the tests completed running. There's literally no indication that anything is happening. VS2010 immediately opened the window to show you that the tests were running.

2. Where are the columns? Most importantly: the error message column. if I'm dealing with multiple test failures, I almost always just need to see the error…

Currently we need to go quite some lengths in order to extend and customize the Microsoft Test Manager functionality (Planning, edition and running tests) because the functionality mtm(.exe) provides only overlaps to a certain extend to our usecases and right now it offers no public API which we can build upon.

I want the ability to associate native C++ Unit tests to Work Items of type Test Case so that I can import these test cases into Microsoft Test Manager (MTM) and run these tests from MTM. We already have a large number of C# unit tests and we have done a large amount of automation around MTM. We do not want to solve this automation problem again for native C++ Unit tests.

I can use parameters while creating action recording and playback for text fields and drop down elements. This does not work for check boxes or radio buttons (For example, if I create a parameter with value "Yes" and use that for a check box, the binding does not work)

Via MTM lab management you can now only see that the lab environment is running tests.

I would like to see which test runs/plans are running and also those that have been queued for running in the lab environment.

Purpose: In a situation where multiple teams can use the same environments for their regression tests, it would be very handy for an admin to see who is running the tests and also which ones are queued.

I use Spec Explorer 2010, a model-based testing tool extension to Visual Studio 2010, to generate automated test cases. It has become an important part of our testing strategy. But the current version only works with Visual Studio 2010.

Please develop a Spec Explorer extension for Visual Studio 2012, so that we can continue to use Spec Explorer to generate test cases as our developers move to Visual Studio 2012.

Currently Microsoft Test Manager allows running only one test suite at a time within a Test Plan. Real testing of any reasonably large system will result in the creation of multiple test suites within a Test Plan, some of which are likely to be Test suites nested within other Test Suites.

Please provide a way for the user to select multiple any or all Test Suites withing a Test Plan and with a single Run "command"