Eclipse Community Forums: Jubula » Discrepancy between headless and through the IDE

Help

Home

Home » Archived » Jubula » Discrepancy between headless and through the IDE(Test fails when headless)

Show: Today's Messages :: Show Polls :: Message Navigator

Discrepancy between headless and through the IDE [message #725077]

Tue, 13 September 2011 21:33

Chris Missing name

Messages: 32
Registered: June 2011

Member

I have two testsuites that I have put into a testjob to be executed. When executing through the UI the tests pass without issue but when I attempt to run them through autrun/testexec the test fails due to a component-not-found exception after passing a couple test cases.

#Resolution:

Setting the -g flag of autrun to false seems to have resolved the component not found issue. Could anyone provide some insight into why this is?

Report message to a moderator

Re: Discrepancy between headless and through the IDE [message #725169 is a reply to message #725077]

Wed, 14 September 2011 06:56

Alexandra Schladebeck

Messages: 1613
Registered: July 2009

Senior Member

Do you have the "Generate names" checkbox in the AUT definition deactivated?
http://help.eclipse.org/indigo/topic/org.eclipse.jubula.client.ua.help/html/manual/node71.html

That would explain the discrepancy.

If you already had it checked, let us know.

Regards,
Alex

Report message to a moderator

Re: Discrepancy between headless and through the IDE [message #725374 is a reply to message #725169]

Wed, 14 September 2011 15:50

Chris Missing name

Messages: 32
Registered: June 2011

Member

Yes generate names is deactivated in the AUT definition. Could you please elaborate on this behavior?

Report message to a moderator

Re: Discrepancy between headless and through the IDE [message #725537 is a reply to message #725374]

Thu, 15 September 2011 06:21

Alexandra Schladebeck

Messages: 1613
Registered: July 2009

Senior Member

Hi,

The name generation option is primarily for making dialog buttons testable on different operating systems. On Windows, the "OK" button is on the left; on some Unix systems and on Mac it is on the right. In the case of standard Eclipse dialogs, this will usually result in the button on the left in a 2-button dialog only being differable from the button on the right by its position in terms of the object mapping. For cross platform testing, this can result in the "Cancel" button being clicked on Linux instead of the "OK" button (or vice-versa, depending on where the mapping was carried out). "Generate names" makes sure that these buttons are identified by something other than their position, so they can be reliably found for cross-platform testing.

When starting your AUT, it's important that the setting for "Generate Names" is the same however you start it. We take care of this for different configurations of the same AUT (the "Generate Names" is a property of the AUT as a whole, not of individual configurations). If you start your AUT using autrun, however, you should ensure that it is using the same property as your configurations. For the default case ("Generate Names" is true), no extra parameters are required in autrun. Once "Generate Names" has been deactivated, however, the -g false flag is required.

Regards,
Alex

Report message to a moderator