Google Code-in

Terasology's Signalling module adds a way to create logic based circuits with a selection of logic gates and triggers. This module was untouched for a while until it was overhauled for GCI so it's in need of touch-ups. One of those is a test plan

All code should have tests, but sometimes it's hard to do that automatically using a program. This is why for a lot of modules Terasology uses Test Plans. These are a series of steps that a developer or tester follows to check that things are working correctly.

Definition of 'Done'

• A detailed test plan (at least 5-10 manual tests) should be submitted to the Signalling module under the wiki page.

  • Either ask a mentor for wiki rights or place it somewhere else like an issue or a wiki on one of your modules.

• An ideal bonus is recording a video of you performing each step in your tests. This video can then serve as a guide for others actually running the tests later.

Where to start

• Look at the example test plan in Rails for the proper formatting of the test case.
• See the Test Plan page for some general information about test plans.

See also

• The task to add javadoc to Signalling
• The task to add a readme to Signalling