|
|
Re: PDE support for running tests in a separate thread [message #36244 is a reply to message #12148] |
Fri, 22 May 2009 14:04 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: jlp.maconomy.com
I noticed that the PDE fix was made for 3.5M5. Does the newest version
of SWTBOT depend on this fix being available? The reason I ask is that I
just installed version 2.0.0.316-dev. Launching that from Eclipse 3.4
seems to force SWTBOT to run on the UI thread. The other team members in
my team experience that SWTBOT does NOT run on the UI thread - they are
using version 2.0.0.204-dev.
-- Jakob.
|
|
|
|
Re: PDE support for running tests in a separate thread [message #36309 is a reply to message #36276] |
Fri, 22 May 2009 14:33 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: jlp.maconomy.com
Hi Ketan,
Yeah, I do that, actually. So, are there any other explanations why it
looks like my tests are run on the UI thread?
Jakob.
Ketan Padegaonkar wrote:
> You need to run the tests SWTBot tests not PDE-junit tests.
>
> -- Ketan
>
> On 22/5/09 19:34, Jakob Lyng Petersen wrote:
>> I noticed that the PDE fix was made for 3.5M5. Does the newest version
>> of SWTBOT depend on this fix being available? The reason I ask is that I
>> just installed version 2.0.0.316-dev. Launching that from Eclipse 3.4
>> seems to force SWTBOT to run on the UI thread. The other team members in
>> my team experience that SWTBOT does NOT run on the UI thread - they are
>> using version 2.0.0.204-dev.
>>
>> -- Jakob.
>
|
|
|
|
Re: PDE support for running tests in a separate thread [message #36620 is a reply to message #36341] |
Mon, 25 May 2009 07:04 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: jlp.maconomy.com
Yes, it returns a non-null value.
And Display.getCurrent() also returns a non-null value (meaning that the
current thread is the UI thread). (I guess getDefault() always returns a
non-null value?)
Jakob.
Ketan Padegaonkar wrote:
> Does Display.getDefault() inside the test give you a non-null value ?
>
> -- Ketan
>
> On 22/5/09 20:03, Jakob Lyng Petersen wrote:
>> Hi Ketan,
>>
>> Yeah, I do that, actually. So, are there any other explanations why it
>> looks like my tests are run on the UI thread?
>>
>> Jakob.
>>
>> Ketan Padegaonkar wrote:
>>> You need to run the tests SWTBot tests not PDE-junit tests.
>>>
>>> -- Ketan
>>>
>>> On 22/5/09 19:34, Jakob Lyng Petersen wrote:
>>>> I noticed that the PDE fix was made for 3.5M5. Does the newest version
>>>> of SWTBOT depend on this fix being available? The reason I ask is
>>>> that I
>>>> just installed version 2.0.0.316-dev. Launching that from Eclipse 3.4
>>>> seems to force SWTBOT to run on the UI thread. The other team
>>>> members in
>>>> my team experience that SWTBOT does NOT run on the UI thread - they are
>>>> using version 2.0.0.204-dev.
>>>>
>>>> -- Jakob.
>>>
>
|
|
|
Re: PDE support for running tests in a separate thread [message #36654 is a reply to message #36620] |
Mon, 25 May 2009 07:37 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: jlp.maconomy.com
Actually, I found the work-around in another thread in this newsgroup:
You have to add the following command-line argument to the
runtime-configuration (even if it runs as an SWTBot Test):
-application org.eclipse.swtbot.eclipse.core.swtbottestapplication
(see the tread "New SWTBot Release"(
--Jakob.
Jakob Lyng Petersen wrote:
> Yes, it returns a non-null value.
> And Display.getCurrent() also returns a non-null value (meaning that the
> current thread is the UI thread). (I guess getDefault() always returns a
> non-null value?)
>
> Jakob.
>
> Ketan Padegaonkar wrote:
>> Does Display.getDefault() inside the test give you a non-null value ?
>>
>> -- Ketan
>>
>> On 22/5/09 20:03, Jakob Lyng Petersen wrote:
>>> Hi Ketan,
>>>
>>> Yeah, I do that, actually. So, are there any other explanations why it
>>> looks like my tests are run on the UI thread?
>>>
>>> Jakob.
>>>
>>> Ketan Padegaonkar wrote:
>>>> You need to run the tests SWTBot tests not PDE-junit tests.
>>>>
>>>> -- Ketan
>>>>
>>>> On 22/5/09 19:34, Jakob Lyng Petersen wrote:
>>>>> I noticed that the PDE fix was made for 3.5M5. Does the newest version
>>>>> of SWTBOT depend on this fix being available? The reason I ask is
>>>>> that I
>>>>> just installed version 2.0.0.316-dev. Launching that from Eclipse 3.4
>>>>> seems to force SWTBOT to run on the UI thread. The other team
>>>>> members in
>>>>> my team experience that SWTBOT does NOT run on the UI thread - they
>>>>> are
>>>>> using version 2.0.0.204-dev.
>>>>>
>>>>> -- Jakob.
>>>>
>>
|
|
|
Re: PDE support for running tests in a separate thread [message #36722 is a reply to message #36654] |
Mon, 25 May 2009 10:13 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Ketan Padegaonkar![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=ketanpadegaonkar%40gmail.com) Messages: 873 Registered: July 2009 |
Senior Member |
|
|
I've fixed this in the latest build available on the update site.
-- Ketan
On 25/5/09 13:07, Jakob Lyng Petersen wrote:
> Actually, I found the work-around in another thread in this newsgroup:
>
> You have to add the following command-line argument to the
> runtime-configuration (even if it runs as an SWTBot Test):
> -application org.eclipse.swtbot.eclipse.core.swtbottestapplication
>
> (see the tread "New SWTBot Release"(
>
> --Jakob.
>
> Jakob Lyng Petersen wrote:
>> Yes, it returns a non-null value.
>> And Display.getCurrent() also returns a non-null value (meaning that
>> the current thread is the UI thread). (I guess getDefault() always
>> returns a non-null value?)
>>
>> Jakob.
>>
>> Ketan Padegaonkar wrote:
>>> Does Display.getDefault() inside the test give you a non-null value ?
>>>
>>> -- Ketan
>>>
>>> On 22/5/09 20:03, Jakob Lyng Petersen wrote:
>>>> Hi Ketan,
>>>>
>>>> Yeah, I do that, actually. So, are there any other explanations why it
>>>> looks like my tests are run on the UI thread?
>>>>
>>>> Jakob.
>>>>
>>>> Ketan Padegaonkar wrote:
>>>>> You need to run the tests SWTBot tests not PDE-junit tests.
>>>>>
>>>>> -- Ketan
>>>>>
>>>>> On 22/5/09 19:34, Jakob Lyng Petersen wrote:
>>>>>> I noticed that the PDE fix was made for 3.5M5. Does the newest
>>>>>> version
>>>>>> of SWTBOT depend on this fix being available? The reason I ask is
>>>>>> that I
>>>>>> just installed version 2.0.0.316-dev. Launching that from Eclipse 3.4
>>>>>> seems to force SWTBOT to run on the UI thread. The other team
>>>>>> members in
>>>>>> my team experience that SWTBOT does NOT run on the UI thread -
>>>>>> they are
>>>>>> using version 2.0.0.204-dev.
>>>>>>
>>>>>> -- Jakob.
>>>>>
>>>
|
|
|
Re: PDE support for running tests in a separate thread [message #36756 is a reply to message #36654] |
Mon, 25 May 2009 10:13 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
Ketan Padegaonkar![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=ketanpadegaonkar%40gmail.com) Messages: 873 Registered: July 2009 |
Senior Member |
|
|
I've fixed this in the latest build available on the update site.
-- Ketan
On 25/5/09 13:07, Jakob Lyng Petersen wrote:
> Actually, I found the work-around in another thread in this newsgroup:
>
> You have to add the following command-line argument to the
> runtime-configuration (even if it runs as an SWTBot Test):
> -application org.eclipse.swtbot.eclipse.core.swtbottestapplication
>
> (see the tread "New SWTBot Release"(
>
> --Jakob.
>
> Jakob Lyng Petersen wrote:
>> Yes, it returns a non-null value.
>> And Display.getCurrent() also returns a non-null value (meaning that
>> the current thread is the UI thread). (I guess getDefault() always
>> returns a non-null value?)
>>
>> Jakob.
>>
>> Ketan Padegaonkar wrote:
>>> Does Display.getDefault() inside the test give you a non-null value ?
>>>
>>> -- Ketan
>>>
>>> On 22/5/09 20:03, Jakob Lyng Petersen wrote:
>>>> Hi Ketan,
>>>>
>>>> Yeah, I do that, actually. So, are there any other explanations why it
>>>> looks like my tests are run on the UI thread?
>>>>
>>>> Jakob.
>>>>
>>>> Ketan Padegaonkar wrote:
>>>>> You need to run the tests SWTBot tests not PDE-junit tests.
>>>>>
>>>>> -- Ketan
>>>>>
>>>>> On 22/5/09 19:34, Jakob Lyng Petersen wrote:
>>>>>> I noticed that the PDE fix was made for 3.5M5. Does the newest
>>>>>> version
>>>>>> of SWTBOT depend on this fix being available? The reason I ask is
>>>>>> that I
>>>>>> just installed version 2.0.0.316-dev. Launching that from Eclipse 3.4
>>>>>> seems to force SWTBOT to run on the UI thread. The other team
>>>>>> members in
>>>>>> my team experience that SWTBOT does NOT run on the UI thread -
>>>>>> they are
>>>>>> using version 2.0.0.204-dev.
>>>>>>
>>>>>> -- Jakob.
>>>>>
>>>
|
|
|
Powered by
FUDForum. Page generated in 0.06049 seconds