• Background
• Test Developers
• Test Publishers
• Test Users
• Technological Issues
• Quality Issues
• Control Issues
• Security/Privacy Issues
• 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. Ensure that you have sufficient understanding of the technical and operational requirements of the test (i.e. hardware and software), as well as the necessary hardware, software and human resources to obtain, use, and maintain the CBT on an on-going basis.
2. Confirm that the system the test-taker is using is documented as being suitable.
3. Ensure there is a good justification for the use of complex software, graphics, and technical IT features in the CBT/Internet test.
4. Monitor supplier for information on future changes to the hardware requirements, test system, or software.
5. Ensure understanding of the implications of changes and their impact on the testing process.

1. Before beginning a test, verify that its robustness has been adequately tested (e.g. documentation provides supporting evidence).
2. Ensure processes are in place to log and resolve problems that may arise during testing.
3. Check availability of the information necessary for contacting the provider of technical support and use technical support services as necessary
4. Inform test publishers/developers where problems occur with the responsiveness of the computer to the test-taker input.
5. For Internet testing, know the recommended procedures for dealing with hang-ups, lost connections and slow downloads, and advise test-takers accordingly.
6. Provide the test-taker with the technical support specified in the test documentation if any routine problems occur.

1. Be familiar with the screen design requirements of the test and ensure that such features are compatible with the systems being used.
2. Ensure that test-takers are informed of screen design conventions, including where instructional text and prompts are placed, and how instructions can be accessed once testing begins.
3. Be familiar with how items are presented and how the test-taker is required to respond.
4. Verify that error messages are non-alarming and inform how to proceed.

1. Check that the hardware/software features facilitate the participation of test-takers with disabilities and those with special needs.
2. Follow best practice as in other modes of testing [see ITC Guidelines on Test Use].
3. Ensure that any necessary test modifications specifically address the test-taker’s special needs and are within acceptable limits so as to not adversely affect score validity.
4. Be aware of the impact these modifications may have on the test-taker’s score.
5. Consider the use of alternative assessment procedures, rather than modifications to CBT/Internet tests, (e.g., paper and pencil test or alternative structured forms of assessment).

1. Understand the technical support documentation provided with the test and how to access additional technical support when needed.
2. Know how to set up, load and log onto the system.
3. Ensure the test-taker has access to information on the test and the testing process before beginning the test and is able to access on-screen help while completing the test.
4. For Internet testing, provide clear information to the test-taker on how to log-in to and off from the system (e.g., the use of passwords).
5. Provide sufficient opportunity for the test-taker to become familiar with the testing software and the required hardware.
6. Where appropriate, direct test-takers to appropriate Internet testing practice sites.
7. Where appropriate, i nform the test-taker about available practice tests. Make it clear that it is the test-taker’s responsibility to practice any embedded tutorials and responses to test items (e.g., use of the input device).
8. Where appropriate, collect data on test-taker reactions towards Internet-delivered testing and provide feedback to test developers to help them ensure a more positive experience for test-takers.