Two Interfaces per test

[djmoffat]

We should be able to build a test that consists of more than one test interface

eg. I may want to perform some likert test then an AB or APE test.

[djmoffat]

Have managed to have one test autoforward to another using the returnURL in setup, but need some way for the save file or reference to be sent over to link the two tests together.

[giuliomoro]

@djmoffat as you asked, my workaround was here and is still online here. The code I was using is here

The trick was using a common string saveFilenamePrefix= in the queryString, such as: http://php-giulio.apps.devcloud.eecs.qmul.ac.uk/waet/test.html?url=hammond/tests/pre_survey.xml&trainingURL=&allowEarlyExit=false&saveFilenamePrefix=61db48e00d29bd6764d709ba8d47b8fe7b8b017a-pre_survey&returnURL=http%3A%2F%2Fphp-giulio.apps.devcloud.eecs.qmul.ac.uk%2Fwaet%2Ftest_base.php%3Fid%3D61db48e00d29bd6764d709ba8d47b8fe7b8b017a%26next%3D1

So it would go back to the home page when the test is done (returnURL) and would prepend some text to the filename (saveFilenamePrefix). A wrapper test_base.php page takes care of generating the unique URL and keep the state through the querystring only (no cookies involved). This is not in that code base but it is here along with some other modifications that were solely intended to help me (and thus were not commited to the main repo).

[nickjillings]

This will be implemented as a standard feature. I will be rebuilding parts of the core to make the interface scripts modular objects that are loaded in. This will allow an interface to be swapped during the test without breaking / hacking anything.

However this will require a lot of work to do so no guarantee on when this will be done.

[djmoffat]

Hey,

What is the status on this. I believe there is now a standard method for doing this? or I am wrong