Skip to content

Test plan first playable

p-kolodziejczyk edited this page Dec 8, 2014 · 2 revisions

Upon presenting a first playable multiple features need to be tested. This document is to provide a rigorous and quantifiable approach towards this testing, so that as much user feedback can be gained as possible. It is desired to involve 4 other students, who had no previous involvement in the game, to test the features. For each around 15 minutes should be needed, including play and detailed questions. 10 minutes is to be spent for play and initial impressions and another 5 for follow-up questions.

General features to test

  • Interface
  • Button layout
  • Appropriateness of texts/messages
  • Game crashing
  • Playability
  • Relation to reality
  • Engagement / Fun

Specific features to test:

  • Starting and ending the game
  • Pausing and continuing the game
  • Menu's overlapping
  • Smooth run without player actions
  • Can any tram be stopped and restarted again
  • Can rerouteing be easily done

Extra questions

  • Does the game start?
  • Do you understand what each button mean at first glance?
  • Do you like the layout? How to improve it?
  • Can you easily start a game?
  • Do you understand what is happening when the game is running?
  • (After disturbance occurs) Do you understand that you need to act and what you need to do?
  • Do you know how to act (where to click etc.)?
  • Can you anticipate the consequences of your actions?
  • Any noticeable bugs or shortcomings?

Home

Timeline

Game Name

Beta Version Requirements

[To do list before Christmas](To-do List before Christmas)

Design Documents

Meetings

Concepts

Useful

Clone this wiki locally