.playlist support?

Hey, is there a feature request already to support a .playlist file as argument? Right now I am using a parser I wrote to parse .playlist files to a .txt file to use with --testlist={pathToFile}.

[CharliePoole]

Strictly speaking, the console itself isn’t extensible although sometimes we make it seem that way. It can use an engine extension, for example, and has special code to deal with some of them.

The teamcity extension is a good example. The console knows it exists and can activate it in response to the --teamcity option but the option had to be hard coded.

I imagine this would work in a similar way. The console would pull test names out of a file and pass them on to the filter builder.

I originally thought about having the console take extensions just like the engine. That’s what the unimplemented “Addins” feature was about. You would bundle an engine extension with a corresponding runner extension needed to make use of it. But the need was never that great considering how simple the console runner is. Might be different with a GUI.

I agree with you that the value is somewhat low for this feature, but it’s also an easy one and can’t currently be implemented except by changing the console.

[ChrisMaddock]

Hey @MPasadu - I presume you’re the guy who asked the same question on Stack Overflow the other day? 😄

To transfer some of my comments - I don’t believe the NUnit console itself should support a .playlist file, but the extensibility of the console should allow for someone to write an extension to do so, which I don’t believe is currently possible.

I don’t believe there is currently any extensibility point to add a test filter. An IFilterProvider extension would be cool - and also the functionality to add custom command line arguments to the console, which I think has been discussed before.

Charlie/Mikkel, what do you guys think? 🙂