Create dummy application for framework testing
Coming from #64 (closed), we want to continue pursuing a test-first approach to building out the framework. To that end, we intend to create a dummy application (task type, operation type) for testing logging and aegir:input functionality.
This will include:
-
an Aegir entity to represent the application, whose function is as a content fixture to exercise key functionality of the system -
one or more Operation types to represent example operations (eg. install, backup, restore) -
one or more Task types to implement the operations -
one or more fields to the Task(s) -
an example "dynamic" task (eg. login link)- followup in #74 -
Add test to demonstrate queue round-trip - follow-up in #58
These will also serve as a reference implementation, exercising all the functionality of the API in a trivial way so we can wrap tests around them, but also provide examples to developers of how to implement more useful applications.