2. Test development
It is better when it’s done by a team.
The desirable qualities for the developers:
native or near native command of the language, intelligence
and imagination.
4. 1.Stating the problem
What kind of test would it be?
What is its precise purpose?
What abilities are to be tested?
How detailed/accurate must the results be?
How important is backwash?
You can take information from tests that have been designed for simmilar
situations. This isn't wrong.
5. 2. Writing specifications for the test
These must be written at the outset.
Includes:
a)content: The entire potential content of any number of versions of a test.
The fuller the information of the content the less arbitrary should be the
subsequent decisions.
6. i.Aspects specified in the content:
1. Operations: scan, skim
2. Types of text: write letters, articles...
3. Addresses of the text
4. Length of texts
5. Topics
6. Structural range: that occur/ should be excluded/ a general
indication
7. Vocabulary range
7. ii. Structure, timing, medium/channel and techniques
Test structure→ sections
Number of items→ in the sections
Medium/ channel→ paper, pencil, online...etc.
Timing→ section and the entire test
Techniques
8. iii. Criteria levels of performance.
Accuracy→
Appropriacy→ Language appropriate to the function?
Range→ vocabulary
Flexibility→ adapt
Size→ more than short- form answers
9. 3. Writing and moderating items.
i. Sampling: Choose wisely from the whole area of content.
ii. Writing items: with specifications in mind/ think like the
test taker/ give a key item.
iii. Moderating items: at least two colleagues.