Unit Testing User Interfaces (Updated!)

Unit testing session

JoseAlmeida's Blog — Mon, 05 Jul 2004 14:06:00 GMT

Unit testing session

JoseAlmeida's Blog — Tue, 06 Jul 2004 03:10:00 GMT

re: Unit Testing User Interfaces

sog1 — Fri, 09 Jul 2004 11:45:00 GMT

Can you list complete code for the tester class including imports, references etc.?

The NunitForms documentation is very lacking.

Thanks

re: Unit Testing User Interfaces

José Almeida — Tue, 13 Jul 2004 21:58:00 GMT

Sure.

First reference the nunit.framework and NUnitForms assemblies (nunit.framework.dll and NUnitForms.dll).

Then you just need to add the following uses:

using NUnit.Framework;
using NUnit.Extensions.Forms;

and the namespace of your class library that has all the forms.

After that it's just as I described above. NUnitForms doesn't have wrapper objects for all the controls (yet), but the ones that are available are the most common and should be enough for most situations.

Anyway, here's a complete listing for a sample test class that uses NUnitForms:
using System;
using NUnit.Framework;
using NUnit.Extensions.Forms;
using DemoWinFormsApp;

namespace NUnitFormsTester
{
[TestFixture]
public class NUnitFormsTest
{
MyForm form;

public NUnitFormsTest()
{
}

[SetUp]
public void SetUp()
{
form = new MyForm();
form.Show();
}

[Test]
public void Test()
{

TextBoxTester MyTextBox = new TextBoxTester("MyTextBox");
ButtonTester MyButton = new ButtonTester("MyButton");
LabelTester MyLabel = new LabelTester("MyLabel");

MyTextBox.Enter("NUnitForms Test");
MyButton.Click();
Assertion.AssertEquals(MyLabel.Text, "NUnitForms Test");
}
}
}

hope it helps!
Cheers!

re: Unit Testing User Interfaces

Hans M. Rupp — Thu, 15 Jul 2004 15:53:00 GMT

Hallo I am trying out NUnitForms and I cannot get it working. I always get a NoSuchControlException:

NUnitFormsTest.GUITest.Test1 : NUnit.Extensions.Forms.NoSuchControlException : TextBox

I cannot figure out what's wrong :-( Looking at the documentation I thought that the controls are accessed by their name.

The program to be tested:
---------------------------------------------------------------
using System;
using System.Drawing;
using System.Collections;
using System.ComponentModel;
using System.Windows.Forms;
using System.Data;

namespace NUnitFormsTest
{

public class Form1 : System.Windows.Forms.Form
{
private System.Windows.Forms.TextBox TextBox;

private System.ComponentModel.Container components = null;

public Form1()
{

InitializeComponent();

}

protected override void Dispose( bool disposing )
{
if( disposing )
{
if (components != null)
{
components.Dispose();
}
}
base.Dispose( disposing );
}

#region Windows Form Designer generated code

private void InitializeComponent()
{
this.TextBox = new System.Windows.Forms.TextBox();
this.SuspendLayout();
//
// TextBox
//
this.TextBox.Location = new System.Drawing.Point(24, 40);
this.TextBox.Name = "TextBox";
this.TextBox.Size = new System.Drawing.Size(240, 20);
this.TextBox.TabIndex = 0;
this.TextBox.Text = "";
//
// Form1
//
this.AutoScaleBaseSize = new System.Drawing.Size(5, 13);
this.ClientSize = new System.Drawing.Size(292, 273);
this.Controls.AddRange(new System.Windows.Forms.Control[] {
this.TextBox});
this.Name = "Form1";
this.Text = "Form1";
this.ResumeLayout(false);

}
#endregion

[STAThread]
static void Main()
{
Application.Run(new Form1());
}

}
}

----------------------------------------------------------------------------------
The test:

using System;
using NUnit.Framework;
using NUnit.Extensions.Forms;

namespace NUnitFormsTest
{

[TestFixture]
public class GUITest : Assertion {
private Form1 form;

public GUITest() {
}

[SetUp]
public void SetUp() {
form = new Form1();
form.Show();
}

[Test]
public void Test1() {

TextBoxTester textBox = new TextBoxTester("TextBox");
textBox.Enter("Test");
AssertEquals("Test", textBox.Text);
}
}
}

Many thanks,

Hans

re: Unit Testing User Interfaces

Robert Livermore — Wed, 04 Aug 2004 20:53:00 GMT

Han,

I have a similar problems with NUNIT. With no solution, yet. In my situation, I have a UI button click that eventually makes an asynchronous SOAP request/response. Hence the SOAP request/response are done an a different thread of execution. In order for the response to repopulate the control requires the response to be copied back to the user's thread. I think this is done by Window's messaging. In order for a form to listen (hook or subclass) into the windows' messaging it must "start" the application by executing "System.Windows.Forms.Application.Run()".

The "Application.Run" when executed is blocked. (Because it is now listening to window's messages). I do not have any threads left to run the Nunit test. I could start a new thread within the nunit test to run the button click, but the information will not be copied back to the proper thread or I have reentrancy problems.

I think there needs to be a change in the NUNIT framework. NUNIT should support another mode. This mode after loading the test assembly into an application domain, should start a thread and execute the "System.Windows.Forms.Application.Run()". When a test is executed, NUnit should add the delegate to message queue (see the BeginInvoke about queuing on the thread that the control's underlying handle was created). I think this should execute a button click the same way a mouse click would.

Robert Livermore B.Sc, MCP, MCSD, MCSE+I, MCDBA
Senior Developer
Cetaris
www.cetaris.com

NUnitForms

wildhope — Mon, 23 Aug 2004 09:21:00 GMT

Ping Back来自：blog.csdn.net