Hi everyone,
I have swapped the execution order of the Velocity setup script (<script> element) and the data source (<dataSource>) inside the <setUp> block of a test case.
Previously, the setup script would be executed and then the data source would add its own variables on top of the resulting Velocity context. However, I thought it would be more useful if the setup script was executed after the current row of data source was loaded, so it could access its variables. We needed this to skip certain partner tracks/activities in the test case template if their mockups were not going to be invoked.
I've pushed the change to bpelunit/master and bluezio/master, as usual. All tests passed :-).
-- Antonio