On 11/21/2012 08:19 AM, Max Rydahl Andersen wrote:
>>>>>> This beckon to question why bot ext was ever
moved in the first place ?
>>>>> We wanted to have ability to change our tests after code freeze
because
>>>>> we have to fix tests once new version of JBT/JBDS is available for
QE.
>>>> the base library for doing tests aren't part of that - that should
just affect the main test code, right?
>>> Unfortunately sometimes we are fixing also bot ext part when new
>>> JBDS/JBT build is available for QE
>> thats a shame :(
> It's reasonable. For example when target platform is changed and Eclipse
> UI behaves differently than previous version we have to fix it within
> bot ext even when some preferences default value is changed.
can you point me to a github commit that outlines this ?
I don't understand why shared code should be affected by target platform change ?
/max
Because when target platform is changed Eclipse UI can change behavior.
I don't know commits but here are examples I remember:
- JBT switched to Juno - SWTBot was not able to find toolbar buttons and
we had to implement workaround
- with target platform changed automatic code completion was introduced
(when there is only one item for code completion it's automatically
inserted when user press Ctrl+Space) and we have to add new shared
method working with this scenario.
Vlado.