|Re: [e4-dev] Failing search console automated tests|
> Yes, they're run as PDE tests. It looks like the code that is calling Test.setupViewAccessor(*) is running before the workbench has completely initialized.
> Is it being started deliberately through OSGi? Most bundles with the "Bundle-ActivationPolicy: lazy" won't run into this problem.
> What is your SWTBot test launching as to run outside the UI thread? What application and/or product does it use?
A successful SWTBot test execution uses “org.eclipse.swtbot.eclipse.core.swtbottestapplication”. According to the test log, the application is “org.eclipse.test.uitestapplication”. So, how do I specify the “-appication” to be the correct one?
From: e4-dev-bounces@xxxxxxxxxxx [mailto:e4-dev-bounces@xxxxxxxxxxx] On Behalf Of Paul Webster
On Mon, Feb 27, 2012 at 3:13 AM, Branekov, Danail <danail.branekov@xxxxxxx> wrote:
The search console JUnit tests are already part of the test execution but there are quite a lot of weird failures:
1. There are quite a lot of IllegalStateExceptions thrown when calling PlatformUI.getWorkbench, for example
java.lang.IllegalStateException: Workbench has not been created yet.
How can the workbench not be created? Tests are executed as PDE tests, right?
What is your SWTBot test launching as to run outside the UI thread? What application and/or product does it use? If the launcher isn't clear, you can always look at the properties of a successful launch in the Debug view, it has the command line used to launch them.
Back to the top