Pre-release of v1.2.2

Test Creator

This is the pre release candidate for v1.2.2 of WAET. This release has been focused on fixing and improving the test creator interface. Instead of the limited candidate before, this one now uses actual web libraries to help with it's very modular layout!

A list of bug fixes: #75, #94, #197, #182, #181, #149, #74, #84, #96, #183

Not fixed right now: #200: Test creator: generate AB(X) test from list of samples - will be deferred to v1.2.3 or some interim point

Core

Several bugfixes and improvements have been made to the core since v1.2.2. As always thanks to all the users and testers who have flagged these issues:

#180, #184, #187, #190, #194, #192, #191, #186, #185, #163, #201, #174, #144, #162, #126, #145, #138, #202, #203, #133, #206, #166, #165, #155, #141, #119, #209, #211,

Specification Changes

There are few new things in the specification from v1.2.1. The core.js is still compatible with v1.2.1 tests (and most v1.2.0). If a test is now invalid, you can load it into the test creator and re-export it with the complete and new syntax! Even less work to convert now!

The new test configuration options are:

#191 Set page positions:

You can now set a page position from the XML. If you have a page you want to always be the first (or last, or any other position) such as for training, you can now enforce that page position. This will also trigger the page to have its alwaysInclude tag set to true as well. <page id='test-1' position="0"> will set the page to position 0 (ie: the first page).

#145 Survey duration and minimum wait times

You can now specify on each survey node a minimum time to complete. This can be useful to enforce regular breaks between pages. The unit is in seconds. An error will appear and be logged if the user attempts to move on before this time has elapsed. <surveystatement id="test" minWait="10">...</surveystatement>

#138 Image element in interface

Want to show images with your test? Now you can. All interfaces support showing an image above the axis. Simply add the image to the axis' <interface> node:

<interface>
    <title>Which sounds most like a drum?</title>
    <image src="https://upload.wikimedia.org/wikipedia/commons/0/0a/Drumkit-icon.png" />
</interface>

You can also add fragment specific images. When the fragment is playing and has an image associated, it will be displayed so long as that fragment is playing:

<audioelement url="0.wav" id="track-0" image="https://upload.wikimedia.org/wikipedia/commons/0/0a/Drumkit-icon.png" />

#133 Custom Error Messages

Instead of the default error messages displayed, you can now add your own:

<interfaceoption type="check" name="scalerange" min="25" max="75">
    <errormessage>Test Error Message</errormessage>
</interfaceoption>

This is only for the range of interfaceoption nodes, so the final check before moving on.

#209 Limit number of plays

You can now specify a minimum and maximum number of plays for your audio fragments. If a fragment has not been played more than or equal to the minimum number then an error is displayed. Likewise a fragment cannot be played more than the maximum number (it simply won't play on the interface and show a notice explaining why).

<setup ... minNumberPlays="2" maxNumberPlays="10"> ... </setup>
<page ... minNumberPlays="2" maxNumberPlays="10"> ... </page>
<audioelement ... minNumberPlays="2" maxNumberPlays="10"> ... </audioelement>

#141 Ordinal Evaluation

A new test type has been added, the ordinal evaluation method. This is a form of discrete ranking where users must arrange the fragments from left to right. This is a discrete method where only one fragment can exist in each location, forcing a decision.

If you find any issues relating to this release please raise an issue report!

V 1.2.1

This release improves the testing platform through implementing a large number of bug fixes. Mostly these should be imperceptible from the previous versions.

Backwards Compatability

All sessions made for earlier versions will work with this version, however a few XML changes have occured. The only significant change is in the structure of the <commentquestion> nodes, which are now wrapped in a container:

V 1.2.0

    <commentquestion id="preference" type="radio">
        <statement>Please enter your overall preference</statement>
        <option name="worst">Very Bad</option>
        <option name="bad"></option>
        <option name="OK">OK</option>
        <option name="Good"></option>
        <option name="Great">Great</option>
    </commentquestion>

V 1.2.1

    <commentquestions>
        <commentradio id="preference">
            <statement>Please enter your overall preference</statement>
            <option name="worst">Very Bad</option>
            <option name="bad"></option>
            <option name="OK">OK</option>
            <option name="Good"></option>
            <option name="Great">Great</option>
        </commentradio>
    </commentquestions>