Google Code-in

The Rails module has gone through a fairly large rework and thus a lot of the test plan is out of date or completely invalid. It covers some features that aren't implemented any more and highlights come bugs that don't exist either.

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.

This task involves going through the existing test plan and updating it. Some feature didn't survive the rework so they currently don't exist, but might come back in the future. In this case, those entries can be crossed out with a strikethrough but not removed.

Definition of 'Done'

• A new test plan (at least 5-10 manual tests) should be submitted to the rails module.

  • 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 through the tests later.

Where to start

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