Commonwealth Computer Navigator's Certificate/Milestone qualityAssurance

From WikiEducator
Jump to: navigation, search

Quality Assurance Tasks for all modules

Strategy for testing and checking of course materials
Test/check requirements
Checking subject matter
Checking editorial style
Functional testing
Technical testing
User testing


The purpose of this document is to outline:

  • the types of testing, checking and evaluation required and when they should occur
  • test criteria
  • the approach for each, and
  • responsibilties.

Test/check requirements

Checking should occur at several levels:

  • subject matter
  • style
  • functional testing
  • technical
  • usability
  • evaluation.

Subject matter

Subject matter experts (SME)provide input into the whole design and development of material. They also check that content is correct and at an appropriate level.

Occurs: Before development, after development.
Responsibility:SME, designer
Document:Subject Matter Expert Review

Editorial style (I think that this is not a feature of this project? Let me know and if so I'll include it. I have not found an editorial style identified. Yes?) For this project editorial checking involves:

  • checking clarity and coherence of structure
  • eliminating ambiguities and imprecise meanings
  • ensuring correct spelling, grammar and usage
  • ensuring that all references are accurate and complete.
Occurs: before and after development
Responsibility:editor, designer

Functional Testing

Functional testing is completed when the material has been loaded into the learning management system, or means of delivery (i.e. cdrom). Its purpose is to:

  • ensure all data has been added
  • check runtime functions
  • ensure all links function as expected.
Occurs:immediately after production
Responsibility: html editor, designer (multimedia and/or instructional), tutor
Document:Functional testing

Technical testing

Techical testing is completed when the material is complete. Its purpose is to:

  • check that links work, pages open, multimedia opens and works
  • ensure browser compatibility
  • check run-times
  • ensure consistency of development
Occurs: after functional test
Responsibility: developer
Document: Technical testing review

Accessibility testing

Accessibility testing is completed when the material is complete. Its purpose is to check:

  • compliance to level one accessibility standards (WAI Priority A)
  • cultural appropriateness
Occurs: after functional test
Responsibility: developer
Document: Accessibility testing review

User testing

User testing ensures that the material is 'fit for purpose'.

Criteria (may) includes:

  • accessibility
  • accuracy
  • adaptibility
  • availability
  • ease of use
  • performance
  • reliabiltiy
  • clarity of instructions, order of tasks etc.

User testing may involve self guided with observors (recommended) or self guided with questionnaire.

Recommended that these sessions are no more than one hour long and have a minimum of 3 people.

Occurs: once edits done, before 'roll out'
Responsibility: designer, developer


Once the material is in use there should be constant evaluation and feedback with regular upgrades.

Occurs: after 'roll out'
Responsibiltity: tutor, user
Documents: none specifically

DRAFT: Editorial guidelines