Thanks for the response. That does look like an easy/clean way to determine if a particular Eclipse view is open.
Unless I am mistaken, it doesn't look like it will actually do the work of opening an Eclipse view if it isn't already showing. There is of course is a limit to exactly what the WindowTester APIs are going to provide to testers. There are some common and general Eclipse UI manipulations (such as opening/closing views, editors, perspectives and such) that could possibly be included in the WindowTester APIs. Not being completely familiar with the WindowTester APIs yet, I thought it would be best to ask the experts about the existence of any such APIs before spending time creating utilities in our test environment.