[MonoDevelop] Continuous builds and unit testing

[Jacob Ilsø Christensen]

Ok, sounds good.

So just to make sure I understand the hierarchy. Say we want to test the
MonoDevelop.Ide.dll assembly.

Add a directory for the tests: monodevelop/Core/src/MonoDevelop.Ide/Test

This directory will have the same directory structure as
monodevelop/Core/src/MonoDevelop.Ide. When running a test, an assembly named
MonoDevelop.Ide.Test.dll will be built. This assembly references
MonoDevelop.Ide.dll and possibly others. Finally nunit-console is run on
MonoDevelop.Ide.Test.dll. Does this sound right? I will add an example test
just to get started.

Should it be make test or make check to run unit tests?

/Jacob


On 11/28/05, John Luke <john.luke at gmail.com> wrote:
>
> On Mon, 2005-11-28 at 19:42 +0100, Jacob Ilsø Christensen wrote:
>
> >
> >         Or if you rather take the incremental approach, how about a
> >         patch that
> >         adds a test and lets see what it would look like.
> >
> > Well, I like the incremental approach. So I will try coming up with a
> > patch doing some tests.
> > A couple of things though:
> >
> > * I take it we should use nunit, so developing MonoDevelop will now
> > require NUnit
> Probably, but I don't think it will need to be an absolute dependency.
>
> > * Do we put test code in the assembly that is to be tested or not?
> > There are pros and cons for both I guess.
> > * How do we exclude test code from release builds (do we want that)?
> > Compiler directives?
> >
> I would personally prefer to do it like the mcs module does it, unless
> there is a compelling reason not to.  Which is a seperate *.Test.dll per
> assembly.  Then we can set it up to run with make check, and only
> developers will have to deal with it.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/monodevelop-list/attachments/20051130/61a9a7cb/attachment.html