ABTest
An uxiverse.com typeAn A/B test is an important tool for improving UX based on data. In such a test, the users are presented with almost identical versions of a page, and only one aspect is varied. Interaction data is collected and compared between both versions. Analysing A/B-tests rely on statistical methods, so one needs a high number of views to yield meaningful results. Testing more than two versions (A/B/C-tests) is possible, but harder to analyze, and even more views are needed.
| Property | Expected Type | Description |
|---|---|---|
| aVersion | UIElement | An A-version is one of the two versions tested in an A/B-Test. The A-version is usually the status quo of the application, and the B-version the changed one that's hoped to bring improved conversion. |
| bVersion | UIElement | A B-version is one of the two versions tested in an A/B-Test. The B-version is usually the 'new' version that is tested against the status quo, which is called the A-version. |
| variation | UIElement | variation of the same UI element, e.g. the A and B version of an A/B-test |
| ContextProperty | Element | A property that holds the context a UI element is in |
| DescriptionFlag | Element | Flags to express that a UI element describes something, e.g. isHelp, isContent, isProgress |
| HierarchyFlag | https://schema.org/Boolean | Flags that express a hierarchical position on an element |
| NavigationProperty | Element | A property that holds the navigation on a UI element, e.g. menu, settings |
| OutcomeProperty | A property that holds a result, output or status | |
| a11y | Element | Properties related to accessibility |
| input | Input is the value/parameter/prop that gets passed to an element in the UX, and can be empty. This applies to visual as well as non-visual elements. |