Eclipse Community Forums: Jubula » Central test data set vs external excel data

Help

Home

Home » Archived » Jubula » Central test data set vs external excel data

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

Central test data set vs external excel data [message #761750]

Wed, 07 December 2011 01:31

Chris Missing name

Messages: 32
Registered: June 2011

Member

The documentation warns against the use of an external excel sheet as the data set over the central data set. Could you elaborate on this recommendation? What are the risks of using Excel?

Report message to a moderator

Re: Central test data set vs external excel data [message #761859 is a reply to message #761750]

Wed, 07 December 2011 07:41

Alexandra Schladebeck

Messages: 1613
Registered: July 2009

Senior Member

Hi,

the question was answered in this post. I'll add the note in the documentation as well.

Best regards,
Alex

Report message to a moderator

Re: Central test data set vs external excel data [message #764276 is a reply to message #761750]

Sun, 11 December 2011 20:26

Chris Missing name

Messages: 32
Registered: June 2011

Member

Thank you for the reply. I feel I am misunderstanding how central data sets are designed. Is it possible to apply a Central Data Set to a testsuite rather than the test cases of each suite? There are many parameters such as timeouts that we would like a single point of maintenance for but I do not see how to accomplish that.

Report message to a moderator

Re: Central test data set vs external excel data [message #764460 is a reply to message #764276]

Mon, 12 December 2011 08:22

Alexandra Schladebeck

Messages: 1613
Registered: July 2009

Senior Member

A central test data set can be applied anywhere where an Excel sheet or a normal data set would be used (i.e. on Test Cases, but not on Test Suites). If multiple Test Cases require the same data, then a central data set can be used to save a) entering the data redundantly for the Test Cases and b) using an Excel table wherein any missing data is not noticed until runtime.

Central definition of timeouts etc. is best done as a part of a module at the moment, as there is currently no real way of defining constants - e.g. you would make your own module from the "Wait for Window to Close" Test Case and set the timeout as a concrete value. You could use variables that are saved at the beginning of the Test Suite via Application Store Value, and reference the variable e.g. $TIMEOUT, but this means you have to remember to execute the store variable Test Case each time (even when you are executing parts of the test), otherwise data will be identified as missing at runtime.

HTH,
Alex

Report message to a moderator