Bug 469360 - Refactor bridge tests
Summary: Refactor bridge tests
Status: NEW
Alias: None
Product: UI Automation
Classification: Mono
Component: Winforms - ATK (show other bugs)
Version: Unspecified
Hardware: Other Other
: P4 - Low : Enhancement
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-26 15:52 UTC by Andres Aragoneses
Modified: 2009-10-28 20:09 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andres Aragoneses 2009-01-26 15:52:39 UTC
Interesting to fix these items:

- Deadlocks on dialog testing.
- Deadlocks on general testing *after* nunit results have been printed. This has already an easy workaround: hit CTRL+C.
- Move each widget test to its own class??
- Reenable Parent testing, and Relation testing.
- Figure out why TreeView/ListView tests screw up the full test suite when enabled.
- Move GailTester static ctor to a TestFixtureSetUp.
- Figure out why the GailTester static ctor sometimes fails with a timeout exception: maybe refactor it to remove Thread.Sleep calls and use AutoResetEvent objects?
- Many elements in BasicWidgetType are only used in BridgeTester. We can remove them from the enum and use GetAdapterForWidget() directly there, instead of GetAccessible().
- Add a Interfaces() call in every test and child test.
- <put your wishlist item here>

Mike, Brad, would you add something here? Feedback appreciated.
Comment 1 Andres Aragoneses 2009-02-06 22:59:22 UTC
Another for the record:

- Bridge tests for dialogs right now must be run separately from the other ones, because otherwise they create a deadlock (without UIA it seems the deadlock doesn't happen).