Operation timed out with Progress Information

[clement]

I have a Progress Information dialog box to do a Job in our application. In WindowTester, while trying to wait/assert for Shell with the Title Progress Information Dialog box, i am getting TimeOut exception. Is it the write way by Checing the shell with the title "Progress Information" to asser that dialog? or other ways are possible?

Code: Select all

ui.wait(new ShellShowingCondition("Progress Information"));
// or
ui.assertThat(new ShellShowingCondition("Progress Information"));


[Phil Quitslund]

Can you confirm (visually) that the progress dialog is indeed popping up before the test times out? If it is, there is also a race condition: if the dialog shows and closes quickly, it might not be there by the time you get to your wait/assert.

As for the "right way" to do it, what exactly are you trying to test? Are you trying to ensure that a certain action causes a Job to get scheduled in Eclipse? If this is the case you could interact with the Job Manager directly. Or are you trying to ensure that your action uses the progress service? Or are you simply trying to ensure that a progress dialog pops up?

[clement]

I can see the progress bar poping up. It is visible nearly some 8-10 secs. I like to ensure that the Action is using Progress service.

[clement]

Here i found some problem that UI execution is blocking the Test Thread.

Code: Select all

long startTime = System.currentTimeMillis();
ui.click(new TableItemLocator("Load Dialog", new ViewLocator("package.views.toolsview")));
System.out.println("TIME Taken" + (System.currentTimeMillis() - startTime));
ui.assertThat(new ShellShowingCondition("Progress Information"));


Output:

Code: Select all

TIME Taken: 15096

[Phil Quitslund]

What is the UI exception? Can you post the stack trace?

[clement]

Here is the Exception Trace.

Code: Select all

com.windowtester.runtime.WaitTimedOutException: Timed out waiting for condition:
toString=shell titled: Progress Information to show
class=com.windowtester.runtime.swt.condition.shell.ShellShowingCondition
   at com.windowtester.runtime.swt.internal.UIContextSWT.wait(UIContextSWT.java:776)
   at com.windowtester.runtime.swt.internal.UIContextSWT.wait(UIContextSWT.java:748)
   at com.windowtester.runtime.internal.AssertionHandler.waitFor(AssertionHandler.java:69)
   at com.windowtester.runtime.internal.AssertionHandler.assertThat(AssertionHandler.java:37)
   at com.windowtester.internal.runtime.UIContextCommon.assertThat(UIContextCommon.java:172)
   at package.uitest.UIDialogTest.testUIComponents(UIDialogTest.java:165)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at junit.framework.TestCase.runTest(TestCase.java:164)
   at junit.framework.TestCase.runBare(TestCase.java:130)
   at com.windowtester.runtime.common.UITestCaseCommon.access$0(UITestCaseCommon.java:1)
   at com.windowtester.runtime.common.UITestCaseCommon$2.run(UITestCaseCommon.java:136)
   at com.windowtester.runtime.common.UITestCaseCommon$3.run(UITestCaseCommon.java:157)
   at com.windowtester.internal.runtime.junit.core.SequenceRunner$1.run(SequenceRunner.java:46)



[Phil Quitslund]

Can you post the basic structure of the action implementation? Is it scheduling a job with the JobManager?

[clement]

Bellow is the code which shows the dialog box,

Code: Select all

    try {
      this.progressService.runInUI(this.progressService, new IRunnableWithProgress() {

        public void run(final IProgressMonitor progressMonitor) {

          progressMonitor.beginTask("imager.......", 10);
          try {
            for (int j = 10; j > 5; --j) {
              progressMonitor.subTask("starting graphics generator");

              Thread.sleep(1000);
              progressMonitor.worked(1);
            }

            int ok = GrapGenWrapper.executeBackend(generatedConfigFile);
            for (int i = 5; i > 0; --i) {
              progressMonitor.subTask("generating graphics");

              Thread.sleep(1000);
              progressMonitor.worked(2);
            }

            if (ok == 1) {
              progressMonitor.worked(10);
            }
            else if (ok >= 5) {
              ShowMessageHelper.showOkMessage(
                  MyDialogImplementation.this.parentShell,
                  Messages.configFile_error);
            }
          }
          catch (Exception e) {
            e.printStackTrace();
          }
          finally {
            progressMonitor.done();
          }
        }
      }, null);
    }
    catch (Exception e) {
      e.printStackTrace();
    }

[Phil Quitslund]

Perfect. Thanks for the snippet. We'll take a look and see what we come up with.

More soon!

[Phil Quitslund]

So, after some time playing with this I haven't been able to come up with anything. The rub is that the UI is totally blocked during the execution of the runnable and no SWT events are generated (such as the ones accompanying shells showing or losing focus). Moreover the progress service does not appear to have any kind of API for monitoring scheduled runnables (e.g., no listeners that get notified during the flight of a runnable). If anyone has any other ideas, I'll be happy to help pursue them!

-phil

[clement]

Will asserting be possible, if we are using the Progress service(Monitoring Progress View) of Eclipse?

[Phil Quitslund]

I'm not sure. On the other hand, if your application uses eclipse Jobs, I'm certain we can assert that jobs have been scheduled (and/or executed). If you want me to explore progress view interactions/assertions feel free to post another snippet and I'll dig in.

[clement]

I finaly able to query the dialog box, by running the service as busyCursorWhile() instead of runInUI()

But i need some suggestion on how will i know the progress bar reached 100%? Is there any helper classes for it?

[Phil Quitslund]

Won't the dialog get dismissed when it reaches 100%? Can you simply wait for it to be dismissed? If it does not get disposed, you've got an error condition... If this doesn't work, feel free to post your modified sample snippet and we'll take a look.

Thanks!

[jerusalem1]

If this is the case you could interact with the Job Manager directly. Or are you trying to ensure that your action uses the progress service? Or are you simply trying to ensure that a progress dialog pops up?