Heh, it's a little confusing ...
The runner(s) are actually used by the concordion:run command (my
least favorite part of Concordion) to run other specifications. These
could be Concordion specs or fit, fitnesse, cucumber, whatever. It
was meant to be used as a way to interact with other frameworks.
If you want to run your tests in another framework like NUnit you will
ahve to write an adapter for NUnit like the Gallio one. The reason I
picked Gallio though is that it can run tests from many frameworks all
together, it has awesome reporting capabilities, etc. so maybe you can
just use it for everything?
I really like your idea of Any.Spec.config ... I will investigate it
tonight.
Thanks
On May 7, 10:49 am, Erlis Vidal <
erlis.vi...@gmail.com> wrote:
> I haven't seen the implementation for the plugin yet. And maybe that's why I
> don't understand something. The Runner expressed in that configuration is
> used by Gallio to locate the Assembly? Or Gallio will use the assembly I
> provide throught the UI?
>
> Another idea is that I would like to Run my Tests using another Test
> Framework, for example NUnit GUI. Is that possible? Is concordion-net tight
> to Gallio?
>
> The idea maybe change a little the design, but the way I see it is as
> follow:
>
> With an assembly *Any.Spec.dll* we should have *Any.Spec.config* (which
> express how to run this specification, I think this file is the current
> concordion.config) With this we will have different config with different
> projects.
>
> Once again, I haven't seen the plugin implementation and maybe isn't
> possible to place the .config in a different location because something
> expressed there could be used by Gallio, but if that is the case, could we
> make two .config files? One for the plugin (with the information needed by
> Gallio) and another with project specific information.
>
> What do you think ?
> Erlis
>