Implement unit tests for System.Windows.Forms drivers

[GoogleCodeExporter]

Benefits: Improved driver support for System.Windows.Forms and regression 
tracking
Requirements: C#/Nunit/Win32 messaging

We would like to have NUnit tests written which can generate Windows.Forms 
applications / events 
to ensure the driver sends the appropriate WM_* message to the correct control.

Links: http://www.mono-project.com
Deliverables: A test suite patch for the SVN repository

Time limit: One week from claim date.

Original issue reported on code.google.com by gro...@gmail.com on 27 Nov 2007 at 4:38

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I was wondering if I could have a little clarification of the requirements. You 
just
want us to create a bunch of NUnit tests which will call standard windows 
events to
make sure that the events are routed to the correct place and then upload the
application and the test class to your svn directory? Also exactly which events 
do
you mean by Windows.Form events. Do you mean every event that a standard 
windows form
has or do we not have to make a button and add a button click event and so on 
for
every type of object possible on a form?

Original comment by cr...@universityprep.org on 29 Nov 2007 at 12:36

[GoogleCodeExporter]

Sure.  I'll make a simple example here (note; this is logic flow, not exact 
flow).

In our driver model when a new window is created (XplatUI.CreateWindow) the 
following messages are sent 
(obviously depending on the CreateParams):

WM_CREATE
WM_SHOWWINDOW
WM_WINDOWPOSCHANGED

We would like additional unit tests that would make minor calls on controls for 
instance to ensure the correct 
messages are received from the driver.

So you will need to debug the win32 message system first to ensure what 
messages are generated and in 
what order, then implement the unit test.

Is that clearer?

Original comment by gro...@gmail.com on 3 Dec 2007 at 3:17