Note that there are some explanatory texts on larger screens.

plurals
  1. POVS2010's Test List Editor functionality in VS2012 (Update)
    primarykey
    data
    text
    <p>Is it possible to get the same Test List Editor functionality from Visual Studio 2010 in Visual Studio 2012?</p> <p>What I would like to do is make a set of lists containing the tests I want to run. When running a list, I want to be able to move tests easily from one list to another. This was easy in VS2010, but with the Test Explorer in VS2012 this isn't possible anymore. I am aware of the Categories functionality, but this isn't what I'm looking for. It maybe in essence does pretty much the same thing like the tests in VS2010's Test List Editor, but requires much much more work.</p> <p>Does anyone know an efficient workaround or plugin or something like that to get the same functionality in VS2012?</p> <p>//UPDATE</p> <p>After a few months of not using SpecFlow I picked up another project using SpecFlow. A few things has changed for testing using SpecFlow in VS2012. Now it is possible to get functionality in VS2012 that comes closes to the functionality described in VS2010. This is what did the trick for me:</p> <ul> <li>Visual Studio 2012 Update 2 introduced the use of playlists;</li> <li>Setting the Test Runner Tool to VisualStudio2012 (Tools -> Options -> Specflow -> General -> Test Runner Tool) gave me te opportunity to run single scenarios by just right-clicking on them and select 'Run Unit Tests';</li> <li>Installing the NUnit Test Adapter let VS2012 discover all my SpecFlow Scenario's and got them to show up in the Test Explorer where they can be put into playlists.</li> </ul> <p>I hope that this update will help people who where running into the same problems as I was.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload