• Background
• Test Developers
• Technological Issues
• Quality Issues
• Control Issues
• Security/Privacy Issues
• Test Publishers
• Test Users
• Official Translations
• Acknowledgements
• References
• Appendix
• Glossary

International Test Commission

International Guidelines on Computer-Based and Internet Delivered Testing

Give due regard to technological issues in Computer-based (CBT) and Internet Testing

1. Provide a clear description of the minimum hardware and software requirements of the CBT. For Internet testing specify browsers which will support the test.
2. Conduct adequate usability testing of the system requirements using the appropriate delivery platforms to ensure consistency of appearance and delivery.
3. Use appropriate technological features to enhance usability and follow established graphical user interface (GUI) design standards. For example, complex graphics and interactive features may reduce software running speed or download time. Items should be designed to fit the test purpose and objectives of assessment, and advanced multimedia features should be used only where justified by validity.
4. Design the system to accommodate likely advances in technology.
5. Design the Internet-delivered testing system to take account of the possibility of fluctuations in demand at different times.
6. Ensure applications of technology advances are tested, documented, and explained to users.
7. Minimise the number of updates and version changes that are issued.
8. Take account of the widely differing connection speeds that apply globally.

1. Test the system to confirm that it is sufficiently robust and capable of dealing with likely system failures and user error.
2. Ensure that the CBT/Internet test is as ‘fail-safe’ as possible in order to minimise problems arising while the test-taker is responding. Where possible and appropriate:
• treat upper and lower case fonts as equivalent,
• prevent operation of keys or controls that have no function in the test,
• eliminate auto-repeat functions of keys,
• prevent a test-taker from exit ing the test by accident,
• provide timely and helpful error feedback,
• follow GUI standards regarding features such as colour, layout, and design, and
• if standardization is not important, allow the user multiple ways to navigate through the system, or allow the user to modify the interface to their liking.
3. When the CBT/Internet test is timed, design the system to respond promptly so that commands have an immediate effect on the screen (e.g., GUI design standards would indicate no more than a 2 second delay onscreen).
4. When the CBT/Internet test is timed, design features so that the time required to move between questions and for the system to record the answer is not part of the timed element (e.g., the test software should deduct these times from the timing of the test or the timing clock should stop during access transitions).
5. For Internet testing, minimise the impact of hang-ups, lost Internet connections and slow downloading (e.g., the system should ensure that no information is lost when the Internet connection is lost).
6. Provide documentation that specifies what to do in the event of routine problems with hardware and/or software.

1. Design systems to follow GUI design standards that have been established by groups such as Human Factors International, including but not limited to:
• ensuring screens have adequate resolution and colour,
• using consistent screen locations and colour for instructional text and prompts,
• using consistent screen design, layout and colours,
• differentiating between test items and test instructions,
• displaying only relevant information on-screen and ensuring the screen is not overfilled,
• placing critical information at the start of the text,
• providing instruction screens with clear fonts and avoiding distracting logos/images,
• allowing test-takers to review or return to the instruction screen(s) where appropriate, and
• ensuring representation of status change of display entities (e.g., dimming, highlighting) is consistent in appearance, and logical and meaningful.
2. Display test name, item number, and test prompts or directions at the same location on the screen for each test page.
3. Produce non-alarming, clear and concise error messages that inform how to proceed. Following an error alert, allow the test-taker to correct any errors and continue the test in the most efficient manner possible.

1. Design CBT/Internet tests with hardware/software (e.g., response format) that facilitates the participation of test-takers with disabilities and special needs.
2. Design CBT/Internet tests with hardware and software that can be modified to allow for appropriate test accommodations (e.g., increased font size).

1. Provide clear, accurate, and appropriate technical support documentation in both electronic and paper formats. Ensure that such documentation is written at an appropriate level for its target audience.
2. Provide clear instructions on how to load and set up the testing system. For Internet testing, information should be provided on how to log test-takers on and off the system.
3. Provide sufficient and easily available on-screen instructions and help for test-takers. This should include, at a minimum, information about the test (number of items, timing, and types of items) and the testing procedure (how to navigate through the system and how to exit).
4. Where appropriate, develop tutorials or practice tests/items that provide test-takers the opportunity to familiarise themselves with the CBT/Internet test.