nunit-core team mailing list archive

[Wolfgang Uhr <692048@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Sorrry it may be more a requested feature ...

In order to handle a message box you have to implement a
ModalFormHandler. If you insert the code, you can send the value of the
the title and the message itself to the console in order to see what has
happened on the "Text output"-Tab. If this works correctly there is no
output on the "errors and failures"-tab.

But if you remove the ModalFormHandler-delegate

1. the result on the "errors and failures"-tab is the message: "Namespace.FunctionName: TearDown : NUnit.Extensions.Forms.FormsTestAssertionException : Unexpected modals: Unnamed, "
2. There is no line idicated which triggers the error

So in case of a large and complex test and then something has changed it
may be very difficult to find the event which triggers the error
message.

I'm reading nunit-discuss@xxxxxxxxxxxxxxxx so in case of further request
we can discuss it there.

Best regards
Wolfgang

Version 2.5.8.10295

** Affects: nunitv2
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/692048

Title:
  An unexpected modal will cause a difficult error message and behaviour

Status in NUnit V2 Test Framework:
  New

Bug description:
  Sorrry it may be more a requested feature ...

In order to handle a message box you have to implement a ModalFormHandler. If you insert the code, you can send the value of the the title and the message itself to the console in order to see what has happened on the "Text output"-Tab. If this works correctly there is no output on the "errors and failures"-tab. 

But if you remove the ModalFormHandler-delegate 

1. the result on the "errors and failures"-tab is the message: "Namespace.FunctionName: TearDown : NUnit.Extensions.Forms.FormsTestAssertionException : Unexpected modals: Unnamed, "
2. There is no line idicated which triggers the error

So in case of a large and complex test and then something has changed it may be very difficult to find the event which triggers the error message.

I'm reading nunit-discuss@xxxxxxxxxxxxxxxx so in case of further request we can discuss it there. 

Best regards
Wolfgang

Version 2.5.8.10295