Google Code-in

Terasology's GooeysQuests is a quest module that adds Gooey, Terasology's slimy mascot, as an in-game NPC that can add a small dungeon to the game world for the player to explore! Your task is to investigate this module's various features and use cases, and create a test plan covering these points.

Definition of 'Done'

• A detailed test plan (at least 10-15 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 GooeysQuests module.

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

Where to start

• Use gradlew fetchModuleGooeysQuests to download the module and try it out! Also, check out its' repository for detailed documentation.
• A high-level overview of the module can be found in this forum thread.
• To get you started with writing the test plan, here are a few examples of functionality that should be verified:
  • The module runs in an otherwise vanilla environment with no crashes or conflicts.
  • The Gooey NPC shows up and prompts the player to generate a dungeon with a skeleton NPC.
  • The template placing tool (obtain using console commands) can be used.

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