What makes a good test?
A good test is: • Mappable to the specification (you must know what portion of the specification it tests) • Atomic (tests a single feature rather than multiple features) • Self-documenting (explains what it is testing and what output it expects) • Focused on the technology under test rather than on ancillary technologies • Correct For a more detailed discussion of these and other test design principles see the HTML4 Test Suite Documentation.
• The test measures what it claims to measure consistently or reliably. This means that if a person were to take the test again, the person would get a similar test score. • The test measures what it claims to measure. For example, a test of mental ability does in fact measure mental ability, and not some other characteristic. • The test is job-relevant. In other words, the test measures one or more characteristics that are important to the job. • By using the test, more effective employment decisions can be made about individuals. For example, an arithmetic test may help you to select qualified workers for a job that requires knowledge of arithmetic operations.
