Recent changes to feature-requests

MessageBoxTester missing members

2010-06-20T18:28:41Z

I think the MessageBoxTester could do with some new members. For example, the ability to retrieve the MessageBox's MessageBoxIcon, MessageBoxButtons, MessageBoxDefaultButton, and the DialogResult that it returns once one of its buttons has been clicked.

I also notice that while it has ClickOk and ClickCancel methods, there is no way to tell it to click the Yes, No, Abort, Cancel or Retry buttons. So if my test brings up a MessageBox which doesn't have a Cancel or OK button, either I need to click the button myself (if I've overridden the UseHidden property to return false) or my test hangs waiting for someone to click a button which nobody can see.

For an example of what I mean, take a look at http://commonforms.svn.sourceforge.net/viewvc/commonforms/CommonForms/CleverMessageBox.cs?revision=21&view=markup (the class being tested) and http://commonforms.svn.sourceforge.net/viewvc/commonforms/CommonForms.Example/NUnitTests/CleverMessageBoxTest.cs?revision=21&view=markup (the test fixture).

I've only just discovered this project and it looks like it can take a lot of the pain out of unit testing winforms classes. Keep up the good work :-)

Simon.

NumericUpDown control tester

2007-09-09T08:12:14Z

Add a tester for System.Windows.Forms.NumbericUpDown control.

ModalFormTester inteface change

2007-08-30T20:47:24Z

Suggest changing ModalFormTester interface. Change "ExpectModal()" method to something like "RegisterModalFormHandler()". This method would no longer accept an "expected" bool. Also, replace "Verify()" with "Invoked()".

My argument is that all assertions should be done by NUnit's Assert utilities. The Verify() function performs a redundant assertion.

For example:
ModalFormTester modalTester = new ModalFormTester();
modalTester.ExpectModal("SomeMessageBox", "SomeHandler", false);
Assert.IsTrue(modalTester.Verify());

This could also be written as:
ModalFormTester modalTester = new ModalFormTester();
modalTester.ExpectModal("SomeMessageBox", "SomeHandler");
Assert.IsFalse(modalTester.Verify());

The redundancy is that Verify() asserts whether the expectations was met. Then Assert also checks that expectation.

This would be cleaner and there is one clear way to use it instead of two:
ModalFormTester modalTester = new ModalFormTester();
modalTester.ExpectModal("SomeMessageBox", "SomeHandler");
Assert.IsFalse(modalTester.Invoked());

ModalFormTester.ExpectModal overlaod for function names

2007-08-30T16:08:53Z

Suggest moving the ExpectModal(string, string [, bool]) overloads from NUnitForms to ModalFormTester. This will allow users to create their own ModalFormTesters but still have the convenience of using ExpectModal with function names instead of Delegates.

Multiple construcotors make the Recorder crash

2007-02-01T22:24:14Z

The recorder crashes when trying to open forms with multiple constructors (additional constructors with parameters)

New API in .NET 3.0

2006-10-12T08:25:32Z

http://windowssdk.msdn.microsoft.com/en-
us/library/ms747327.aspx

Easy and powerfull for GUI testing.

You have a plans to use it?

kOSt

Support for .NET 2.0 menu strips

2006-08-28T13:30:34Z

The current MenuItemFinder is unable to find menu
items in the .NET 2.0 menu strips. Is there an ETA
for when this will be added?

Thanks,
Adam

New design project

2006-08-06T16:22:59Z

Sorry for VB

Interface Promoute

2006-08-06T09:43:24Z

See File Attached for new design Recorder Utility

Fast adding VB scripting

2006-08-06T09:28:25Z

May be tolk about this with buddie form
http://www.kamalpatel.net/

It has a library with which and zero forces users can
select VB or C#