Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Oomph » How to suppress the Questionnaire in automated tests?
How to suppress the Questionnaire in automated tests? [message #1468173] Mon, 10 November 2014 16:36 Go to next message
Christian W. Damus is currently offline Christian W. DamusFriend
Messages: 1199
Registered: July 2009
Location: Canada
Senior Member

Hi,

When I run JUnit test suites locally in my Oomph-provisioned IDE, it
often happens (but not always; I'm not sure why) that the Questionnaire
dialog opens, partially covering the workbench window and capturing
input focus (because it's modal). Worse, sometimes the
Display.syncExec() call that launches this dialog causes the UI thread
to be interrupted while CDO's plug-in container is waiting on a lock
during its activation, which then throws an InterruptedException that
bombs the CDO core plug-in's activation, resulting in
NoClassDefFoundErrors on various CDO classes. The consequence of that
is all kinds of exceptions and errors bombing my tests.

So, the short of it is that I'd like to suppress this questionnaire
dialog during test execution. I could remove the oomph plug-ins from
my test launch configurations, but these are shared with the rest of
the Papyrus team in the Git repository and it would result in all of
the plug-ins that *are* included being listed in the launch
configuration XML, which I don't want.

Is there a system property I can set in the launch configuration, or
some other non-intrusive means by which I can suppress the
questionnaire dialog at run-time?

Thanks,

Christian
Re: How to suppress the Questionnaire in automated tests? [message #1468226 is a reply to message #1468173] Mon, 10 November 2014 17:33 Go to previous messageGo to next message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6487
Registered: July 2009
Senior Member
Am 10.11.2014 um 17:36 schrieb Christian W. Damus:
> Hi,
>
> When I run JUnit test suites locally in my Oomph-provisioned IDE, it often happens (but not always; I'm not sure why)
> that the Questionnaire dialog opens, partially covering the workbench window and capturing input focus (because it's
> modal). Worse, sometimes the Display.syncExec() call that launches this dialog causes the UI thread to be interrupted
> while CDO's plug-in container is waiting on a lock during its activation, which then throws an InterruptedException
> that bombs the CDO core plug-in's activation, resulting in NoClassDefFoundErrors on various CDO classes. The
> consequence of that is all kinds of exceptions and errors bombing my tests.
That sure sounds very scary! We should probably add a -D thingy to suppress the questionnaire.

But independent of that I wonder why that happens in the first place. I assume you've run through the quesionanaire
already once? That should have modified your user.setup such that the next time you (i.e. your user account) launch
anything (an IDE, a test or whatever) the questionnaire doesn't pop up again. I noticed myself here and there that the
questionnaire-was-shown flag gets lost/overwritten, but in all cases it boiled down to a pre-questionnaire Oomph being
involved. Could it be that your TP contains a slightly outdated Ooomph?

>
> So, the short of it is that I'd like to suppress this questionnaire dialog during test execution.
Please submit a bugzilla as a reminder for me.

> I could remove the oomph plug-ins from my test launch configurations, but these are shared with the rest of the
> Papyrus team in the Git repository and it would result in all of the plug-ins that *are* included being listed in the
> launch configuration XML, which I don't want.
Understandable! Why is Oomph in your TP at all?

>
> Is there a system property I can set in the launch configuration, or some other non-intrusive means by which I can
> suppress the questionnaire dialog at run-time?
No, but I'd like to add one ;-)

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper


Re: How to suppress the Questionnaire in automated tests? [message #1468297 is a reply to message #1468226] Mon, 10 November 2014 18:42 Go to previous message
Christian W. Damus is currently offline Christian W. DamusFriend
Messages: 1199
Registered: July 2009
Location: Canada
Senior Member

Thanks, Eike,

I've raised enhancement request 450871 [1].

I have run through the questionnaire, yes, on a different install and
workspace (this one is "grandfathered"). But, IIRC, some of the
questions are workspace-specific, so I would expect it to be run once
for every new workspace anyways, right? And that's perfectly fine.

My TP includes Oomph because in the Papyrus project we have some
developer tools that extend Oomph for semi-automated management of the
papyrus.setup model, so to work on those tools in our workspaces, we
need Oomph in the TP. My latest TP update is less than a week old.

Our test launch configs all just take the entire set of TP+WS plug-ins,
which is fine, but that happens to include the setup UI and
questionnaire, which will also be fine once I can block the
questionnaire dialog.

BTW, I would be remiss if I did not make it clear that I like the
questionnaire! It's a great out-of-the-box experience for Eclipse
(about 11 years overdue). It's just that it cannot help some bizarre
interactions in our test execution.

Christian


[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=450871



On 2014-11-10 17:33:41 +0000, Eike Stepper said:

> Am 10.11.2014 um 17:36 schrieb Christian W. Damus:
>> Hi,
>>
>> When I run JUnit test suites locally in my Oomph-provisioned IDE, it
>> often happens (but not always; I'm not sure why) that the Questionnaire
>> dialog opens, partially covering the workbench window and capturing
>> input focus (because it's modal). Worse, sometimes the
>> Display.syncExec() call that launches this dialog causes the UI thread
>> to be interrupted while CDO's plug-in container is waiting on a lock
>> during its activation, which then throws an InterruptedException that
>> bombs the CDO core plug-in's activation, resulting in
>> NoClassDefFoundErrors on various CDO classes. The consequence of that
>> is all kinds of exceptions and errors bombing my tests.
> That sure sounds very scary! We should probably add a -D thingy to
> suppress the questionnaire.
>
> But independent of that I wonder why that happens in the first place. I
> assume you've run through the quesionanaire already once? That should
> have modified your user.setup such that the next time you (i.e. your
> user account) launch anything (an IDE, a test or whatever) the
> questionnaire doesn't pop up again. I noticed myself here and there
> that the questionnaire-was-shown flag gets lost/overwritten, but in all
> cases it boiled down to a pre-questionnaire Oomph being involved. Could
> it be that your TP contains a slightly outdated Ooomph?
>
>>
>> So, the short of it is that I'd like to suppress this questionnaire
>> dialog during test execution.
> Please submit a bugzilla as a reminder for me.
>
>> I could remove the oomph plug-ins from my test launch configurations,
>> but these are shared with the rest of the Papyrus team in the Git
>> repository and it would result in all of the plug-ins that *are*
>> included being listed in the launch configuration XML, which I don't
>> want.
> Understandable! Why is Oomph in your TP at all?
>
>>
>> Is there a system property I can set in the launch configuration, or
>> some other non-intrusive means by which I can suppress the
>> questionnaire dialog at run-time?
> No, but I'd like to add one ;-)
>
> Cheers
> /Eike
>
> ----
> http://www.esc-net.de
> http://thegordian.blogspot.com
> http://twitter.com/eikestepper
Previous Topic:evaluating boolean variables to control installation
Next Topic:Question about VariableTask precedence and <restriction>
Goto Forum:
  


Current Time: Wed Apr 01 01:06:02 GMT 2020

Powered by FUDForum. Page generated in 0.03137 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top