Reporting Template
Use the following checklist to assure that required elements are reported. Use the ones that are relevant for your testing purpose, method and setting.
NOTE: this works as checklist, thus, descriptions can be very brief. As mentioned above, not everything mentioned has to be described.
NOTE: this template is meant to be used for reporting all kind of tests -not only questionnaires. In addition, how pedagogical partners report for their own questionnaires or research reports is up to them. This template concentrates on the usability test reporting.
Title Page
TITLE
Subtitle if needed
Due date of deliverable: xx.xx.2012
Start date of project: xx.xx.2012
Product name and version: |
Tool name, M xx version (proto or stable version) |
|---|---|
Organisers of the test: |
Xxxxx |
Date of the test: |
Xxx, xxx |
Date of the report: |
Xxx,xxx |
Editor: |
Xxx |
Contact name(s): |
Xxx |
Executive summary
Provide a brief level overview of the test (including purpose of test) |
Name the product |
|
|---|---|---|
Method 1 |
|
|
Number and type of participants |
|
|
Tasks (if task are used) |
|
|
Method 2 |
|
|
etc |
|
|
Results |
Results in main points, e.g. bullet list (this is needed for being able to get the main results without reading the full report, this is seen as important, since the reports serve different purposes and sometimes the need is to get a fast overview) |
|
Table of contents
Title Page....................................................................................................................... 1
Introduction............................................................................................................... 2
Full Product Description....................................................................................... 2
Test Objectives.......................................................................................................... 2
Method...................................................................................................................... 3
Participants............................................................................................................ 3
Context of Product Use in the Test....................................................................... 3
Test Facility........................................................................................................... 3
Experimental Design.................................................................................................. 4
Results....................................................................................................................... 4
Introduction
Full Product Description
- Formal product name and release or version
- Describe what parts of the product will be/were evaluated
- The user population for which the product is intended (link to the personas)
- State the objectives for the test and any areas of specific interest
- Functions and components with which the user directly and indirectly interacted
- Reason for focusing on a product subset
- The total number of participants tested
- How participants are to be/were selected; whether they had the essential characteristics
- Differences between the participant sample and the user population
Test Objectives
Method
Context of Product Use in the Test
- Any known differences between the evaluated context and the expected context of use
- Tasks (if tasks are used in the test)
- Describe the task scenarios for testing
- Explain why these tasks were selected
- Describe the source of these tasks
- Include any task data given to the participants
- Completion or performance criteria established for each task
Test Facility
Describe the setting, and type of space in which the evaluation was conducted
Participantʼs Computing Environment
- Computer/smart phone, tablet configuration, including model, OS version, settings,
- Browser/app name and version;
- Relevant plug-in/or other additional apps, names and versions
Display Devices (report if relevant for the particular test, often needed when e.g., Paper prototypes are tested or static prototypes are tested on screen)
- If screen-based, screen size, resolution, and colour setting
- If print-based, the media size and print resolution
Test Administrator Tools (report if relevant for the particular test)
- If a questionnaire was used, describe or specify it here (add these to appendix)
- Describe any hardware or software used to control the test or to record data (audio, video)
- Define independent variables and control variables
- Describe the measures for which data were recorded (the scale/scope of the recorded data, if relevant for the particular test, i.e., written notes, think aloud in audio recording, etc.).
Participant General Instructions (here or in Appendix)
- Instructions given to the participants
Data analysis
- Quantitative data analysis
- Qualitative data analysis
Results
Presentation of the Results
- From quantitative data analysis
- From qualitative data analysis (descriptive and clarifying presentation of the results)
Summary Appendices (if any)
- Custom Questionnaires_, (if used)_
- Participant General Instructions
- Participant Task Instructions, if tasks were used in the test