Google Code-in

Terasology's Cities module procedurally generates cities within the game's world - these include pre-built structures as well as roads and walls. It serves as a basis for several other modules - StaticCities creates cities at world-gen time, while DynamicCities introduces advanced behaviour such as city growth and population simulation. Your task is to investigate the Cities module'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 Cities module, as well as the StaticCities and DynamicCities extensions.

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

Where to start

• Use gradlew fetchModuleX to download the modules and try them out! Also, check out their repositories for detailed documentation.
• A high-level overview of the base Cities module can be found in this forum thread.
• To get you started with writing the test plan, here are a few examples:
  • The modules run without immediate crashes or dependency conflicts.
  • Cities exist in-game and are properly generated.

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