Platform Team/Server Kit/Architecture: Difference between revisions
Rename Sugar Serve to Sugar Server Kit |
|||
| Line 71: | Line 71: | ||
It is an entirely downstream decision as to how to deploy Sugar Server Kit based solutions. | It is an entirely downstream decision as to how to deploy Sugar Server Kit based solutions. | ||
== Development model == | |||
Having a decent testing infrastructure is the major intention for [[Sugar Server Kit]] components. Every component needs to have, at least, unit tests for its internals. Components like [[Sugar_Server_Kit/sugar-server]] have also integration tests to cover integration issues for its parts. | |||
Except component specific tests, it is important to have system integration testing when all components are being tested in collaboration. In that case, the [[Sugar_Server_Kit/sugaroid|sugaroid]] component, sugar client bot, will help. | |||
The reliable testing environment should help with avoiding regressions while following [[Sugar Server Kit]] [[Sugar_Server_Kit/Release plan|statement of purpose]] for releases. | |||
== Components == | == Components == | ||