[NEW RELEASE VERSION 3.0.0] The QTaste is an open-source functional and non-functional test environment offering services to developers and testers. It has been implemented following a data driven testing philosophy.
We’ve noticed a problem with QTaste 3.0.0 when the testapi implementation changes between two testbeds.
You can reproduce it with the attached files.
The run on the first testbed is OK
MAIN VALUE: 1
SUB VALUE: 1
MAIN VALUE: 2
SUB VALUE: 2
The run on the second testbed of the same test script is NOK
MAIN VALUE: 1
SUB VALUE: 2 <- CORRUPTED ! The TestData file is not read anymore in the sub library!
MAIN VALUE: 2
SUB VALUE: 2
Instead of adding javagui, you can import anything (i.e. I’ve tried with com.qspin.qtaste.testapi.impl) and it introduces a corruption of the reading of the testdata.
We’ve noticed a problem with QTaste 3.0.0 when the testapi implementation changes between two testbeds.
You can reproduce it with the attached files.
The run on the first testbed is OK MAIN VALUE: 1 SUB VALUE: 1 MAIN VALUE: 2 SUB VALUE: 2 The run on the second testbed of the same test script is NOK MAIN VALUE: 1 SUB VALUE: 2 <- CORRUPTED ! The TestData file is not read anymore in the sub library! MAIN VALUE: 2 SUB VALUE: 2
Instead of adding javagui, you can import anything (i.e. I’ve tried withcom.qspin.qtaste.testapi.impl ) and it introduces a corruption of the reading of the testdata.