Manual Testing

There are many unit tests for Geppetto, but some things are harder than others to test; such as that the packaging is correct and that when all the pieces are brought together that they do what is expected.

Here are some things to test:

• Create a new empty module project - expect one to be created
• Write a manifest that uses a function from the platform (say debug("foo")) - it should be found
• Try the "Open declaration" function and the reverse "Find references" between two project (i.e. one manifest refers to a class in another project). - Expect that it validates ok and that navigation is possible.
• Write a custom ruby function in a module that is visible to another module. Ensure it validates ok.
• Create a project from a module on the forge. Expect that such a project is created.
• Ensure that help pages are in place.

These steps check that the IDE way of building, index construction and use works, and that the Ruby parsing module is in place as well as a functioning forge API.

When there are changes to the platform

• Ensure that preferences pages include all required pages (basically click through all links in all preference pages to ensure there are no changes in the platform that needs to be reflected in the set of preference pages included in packaged Geppetto).