|
Bugzilla – Full Text Bug Listing |
| Summary: | Unit tests should fail when finding a Log.Error event | ||
|---|---|---|---|
| Product: | [Mono] UI Automation | Reporter: | Andres Aragoneses <aaragoneses> |
| Component: | Winforms - General | Assignee: | E-mail List <mono-a11y-bugs> |
| Status: | REOPENED --- | QA Contact: | E-mail List <mono-a11y-qa> |
| Severity: | Major | ||
| Priority: | P2 - High | CC: | forgotten_oDRaEXi7Ku, mgorse |
| Version: | Unspecified | ||
| Target Milestone: | Release 1.1 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Proposed patch | ||
|
Description
Andres Aragoneses
2009-03-13 17:25:04 UTC
Good idea. Could do this by have an event on the Log object when errors are logged...could hook into that in fixture setup. Is that too convoluted? Created attachment 304536 [details]
Proposed patch
It's weird, the post-review script is not working for me now, so I'm attaching the patch here for now.
Move all P1 and P2 bugs into Release 1.1 milestone. Fixed in r137970. I reverted this behavior in a commit yesterday. I think that we'd decided on removing it, and I had it removed locally anyhow because the tests were aborting because of an error that UiaDbusBridge was generating (which had nothing to do with UiaAtkBridge). (In reply to comment #5) > I reverted this behavior in a commit yesterday. The commit was r154393. Mike: I have an idea. Why don't you enable this again but, instead of having an Assert.Fail() call in the reception of the error, you could raise some exception (InvalidOperationException), so you can catch it in the exact failure you were getting, but nowhere else. This way we can mark this bug as FIXED again and you don't get the UiaDbusBridge failure. Let me know what you think. |