Preconditions for ending development

• Changelogic
• Getting Started
• End Development Conditions

Why use preconditions? The preconditions are used to avoid trivial shortfalls in committed changes to save review and integration time.

The purpose of isolated changes in Changelogic is to ensure that code is reasonably bug-free and complies company standards before reaching other developers. The flaws would be much harder to fix once other developers have started to depend on the code and copy-pasted parts of it elsewhere. It would be a waste of time to integrate and resolve conflicts in code that would ultimately not even compile.

In order to assist ensuring compliance to such quality criteria, various checks may be automated and required to pass before ending development of a change. For example, applying beautifier, compiling the whole project and running some unit tests are quite common among our users. Any action that can be run by a build script may be specified as a precondition to ending development, including other targets of the build script.

The checks to perform should be inserted into build script of the project (build.xml) target “end_edit” before calling Changelogic script to handle ending development (the line <ant ...>).

If the preconditions generate some report (e.g. unit test summary, test coverage report), the report can be uploaded to Changelogic in order to have it accessible via detail form of the change. Read how to configure the build script for more information.