Google Code-in

Terasology's engine is the heart and soul of the game, containing core systems and APIs that all other facades and modules depend on. Your task is to investigate the engine's various features and use cases, and create a test plan covering these points.

Definition of 'Done'

• A detailed test plan (at least 20-25 manual tests) is submitted as a forum post, GitHub wiki page etc. The test plan should be systematic instructions on how to (manually) test the identified features, covering the different usage scenarios (what should be done?) and the expected outcome (what should happen?). It should cover different features from the game's core engine, excluding any modules - these are covered in separate tasks.

• An ideal bonus is recording a video of the tests that can be used to guide later testing.

Where to start

• Download the game and try it out! The game's wiki will probably be of help.
• To get you started with writing the test plan, here are a few examples of functionality that should be verified:
  • Launch the game.
  • Select, activate and deactivate different modules.
  • Change input mappings.
  • Change the player name.
  • Join and leave multiplayer sessions without leaving the game client hanging (no orphaned stalled process).

See also https://github.com/MovingBlocks/Terasology/wiki/GCI#test-plans