Collecting Ideas About New Console Runner

4 views
Skip to first unread message

Charlie Poole

unread,
Dec 13, 2009, 2:57:02 PM12/13/09
to nunit-...@googlegroups.com
Hi All,

I'm adding some revisions to the console runner spec started by
Andreas and I thought I'd informally poll you about a few points.
I'd appreciate your comments on any or all of them.

The 3.0 version of nunit-console should be reasonably similar
to the 2.5 version, but will not be 100% compatible. I've tried
to cover all incompatibilities below. Options not listed will
continue to work as before

1. Command line should accept single or multiple assemblies
and/or projects (The 2.5 version accepts multiple assemblies OR a
single project, but not a mix.)

2. The runner will provide very little functionality itself, but
will delegate test loading and execution to the new NUnit test
engine in order to provide identical results between the console,
the gui and any other test runner.

3. The currently deprecated /fixture option will be removed and
the existing /run option will be expanded to allow it to be
used more than once on the command line. The distinction between
filtering tests at load time versus execution time is meaningless
in the console runner anyway. We may be able to optimize loading
when the /run option is used, but that doesn't need to be exposed
at the command line.

4. The run option will allow limited regular expressions.

5. There will be some (TBD) revision or replacement of the /include
and /exclude options to resolve the 'hyphen' problem and expand
the ability to use category expressions. One possibility is a
sql-like syntax.

6. The /process and /domain capabilities will be retained but
possibly combined into a single option, name TBD. Remote process
execution will be added.

7. The display of dots to indicate progress will be replaced by
an approach that uses less screen space and the /nodots option
will be removed.

8. The /xmlconsole option, which streams xml to stdout and
suppresses all other output will be removed

9. The /nothread option will be removed, since it is a bit
confusing and is not needed. Currently, nunit creates a number
of threads and the option only eliminates one of them.

10. I'm not sure about the /noshadow option. I'd like some
feedback from those who would be affected if either dropped
it. I'd also like to hear comments about whether we need to
shadow copy at all under the console runner.

Charlie





Steven Whatmore

unread,
Dec 13, 2009, 3:07:52 PM12/13/09
to nunit-...@googlegroups.com
This might be the wrong method or forum for this but one of the major issues that we have encountered with the Console-runner is the integration with Visual Studio and other tools, particularly the version of the nUnit DLL and incompatibilities with versions used by various other frameworks (i.e Spring)

I know that there are numerous posts and query regarding how to fix that using assembly-redirect and various other methods but believe me it is not straight-forward.

If I get to vote I would say please address this issue

Now that I think about it this probably more for the GUI-runner but also applies here

Steve Whatmore, MBA, MCP, .NET
Senior Architect
416.598.1241 x245
-------------------------------------------------
PureFacts Financial Solutions
372 Bay Street, Suite 1400
Toronto, Ontario M5H 2W9
416.598.1241 main
888.596.9338 toll free
416.598.9226 fax

www.purefacts.com


PureFacts Financial Solutions is a Lynxdev Company
Please consider the environment before printing this e-mail.
This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately.
Ce courrier électronique est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courrier électronique par erreur, veuillez m'en aviser immédiatement, par retour de courrier électronique ou par un autre moyen.
--

You received this message because you are subscribed to the Google Groups "NUnit-Discuss" group.
To post to this group, send email to nunit-...@googlegroups.com.
To unsubscribe from this group, send email to nunit-discus...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nunit-discuss?hl=en.


Charlie Poole

unread,
Dec 13, 2009, 3:21:44 PM12/13/09
to nunit-...@googlegroups.com
Hi Steven,

Currently, there are no particular VS-compatibility objectives for
the console runner, beyond importing VS files. Would you like to take
a shot at defining such objectives?

Any VS-specific objectives (like opening VS projects) will be dealt
with in extensions rather than in the base console runner itself,
but for now it's probably easier to talk about it as if the runner
were responsible.

Also, if you have encountered some major issues, have you filed
bug reports on them?

Charlie

Kenneth Xu

unread,
Dec 16, 2009, 11:36:38 PM12/16/09
to nunit-...@googlegroups.com
All seems good stuff to me. And I don't think shadow if necessary for
console runner.

Cheers,
Kenneth

Reply all
Reply to author
Forward
0 new messages