Working with unsupported controls in NUnitForms

by Paul 3/20/2007 11:32:00 PM

Another sequel to the entry on "Getting Started with NUnitForms"

http://www.pksoftware.net/devblog/post/2007/02/Getting-Started-With-NUnitForms.aspx

This post is focused on compiling the latest NUnitForms code from sourceforge.

I have seen/heard/had a few questions about testing windows forms controls that are not currently supported by NUnitForms (specifically ".Net 2.0 NUnitForms alpha 5 release" - http://sourceforge.net/project/showfiles.php?group_id=95656).

There are 2 answers...

Cut your own (see the "How to add Control Testers" section at http://nunitforms.sourceforge.net/docs.html), or
Get the latest source out of the subversion repository and use the generic tester class...

The subversion connection details are here: http://sourceforge.net/svn/?group_id=95656

You will need TortoiseSVN (http://tortoisesvn.net/) or similar to get the files.

Note that all related files for the build are also downloaded (nant, nunit, ncover and ndoc etc) so there won’t be any messing around trying to find the correct library dependencies (ahhh!) Of course, because of this the download is about 8.5mb...

Now... from here on in things could get a little messy. You could have problems with key containters, there may be a duplicate "ButtonTestser.cs" file... The list was getting a little long - the short answer to the "problems" were to compile the NUnitForms project after modifying the signing method of the 2 projects "NUnitForms" and "NUnitForms.ScreenCapture". You will also need to delete the AssemblyKeyName code references in the relevent AssemblyInfo.cs files.

Keep in mind that when you get the latest out of a code repository this sort of thing is not unexpected or "bad". Its a work in progress...

Now the latest build of the NUnitForms DLL will give you access to the generic control tester class. When you need to test a control that does not have its own tester class (e.g. ButtonTester) you can use the generic declaration and create your own tester class, e.g. for a picture box:

public class PictureBoxTester : ControlTester<PictureBox, PictureBoxTester>
{
// Now implement each overloaded constructor calling the base class
public PictureBoxTester() {}
public PictureBoxTester(string name, Form form) : base(name, form) {}
public PictureBoxTester(string name, string formName) : base(name, formName) {}
public PictureBoxTester(string name) : base(name) {}
public PictureBoxTester(ControlTester tester, int index) : base(tester, index) {}
}

Now in the tests you can create tester objects and access all the properties and perform clicks etc:

[Test]
public void ExamplePropertyCheckAndDoubleClickTest()
{
PictureBoxTester picTester = new PictureBoxTester("pictureBox1");
Assert.AreEqual(@"C:\dir\somePic.bmp", picTester.Properties.ImageLocation);
picTester.DoubleClick();
}