NUnitLite could process multiple assemblies
See original GitHub issueCurrently in the built-in runner in nunitlite, TextUI correctly captures multiple assemblies on the command line, but then only processes the first of them.
// TODO: For now, ignore all but first assembly
Assembly assembly = _assemblies[0];
Is there a reason that all assemblies provided could not be processed? It would be seem to be beneficial to be able to.
Issue Analytics
- State:
- Created 9 years ago
- Comments:29 (29 by maintainers)
Top Results From Across the Web
Engine Parallel Test Execution
Parallel execution is the default behavior when running multiple assemblies together using the nunit3-console runner. Normally, all the test processes run ...
Read more >Run NUnit3 tests in parallel from multiple assemblies ...
1 Answer. You haven't told NUnit to run the two assemblies in parallel processes. Add --process:Parallel to your command-line. Suggest reading ...
Read more >NUnitLite Options
Several options allow selection of a subset of the tests in an assembly for execution or display. The --prefilter option operates first. If...
Read more >running NUnit tests in parallel
Currently NUnit has no way to run tests in parallel, you will most likely have to ... high level - by running multiple...
Read more >CHANGES.txt
If multiple assemblies are run in separate processes, this value may be used to limit the number that are executed simultaneously in parallel....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@nunit/framework-team I propose we wrap this up once and for all. From our discussion, it’s clear that we want nunitlite to be for primarily for self-executing tests. A secondary use is for single assemblies that can’t be self-executing because of their platform. In that case, nunitlite-runner is used to pass a single assembly to nunitlite.
To handle both cases, I propose we eliminate the detection of a file on the nunitlite command-line and let the runner do it. The runner can pass the identity of a pre-loaded assembly using a special interface, separate from AutoRun, which handles the main, self-executing case.
Comments?
I agree, I think the standard AutoRun should just execute the current assembly, or you should pass in the assembly (in code) that you want to execute.