Integration Manager Checklist
This page is developed as a checklist for integration managers. it is still work in progress
- Correctness of the code
- That the code can compile and integrates on the system of the integration manager
- No test cases fail
- The code adheres to the coding guidelines
- Documentation of the code is easily understandable, no missing comment/documentation
- The ticket must be linked to the requirement document and/or analysis documentation which must be provided in the Confluence Wiki system (in fact the ticket should not directly link Confluence, but rather should the Confluence page name the ticket, the backlink is provided by Jira/Confluence)
- The realization of the functionality must adhere to the given requirements/analysis documentation on Confluence
Files that should only change if there is a reason
Area | Files | Affects | Comments |
|---|---|---|---|
Libraries | .ivy | Ivy configuration and thus libraries | new libraries must always be tested and should not be added for the fun of it |
Libraries | .ivysettings | Ivy configuration settings | possibly someone removed resolvers, which is not good |
Libraries | .jar |
| new jar files should only be added if they are necessary and if they cannot be resolved using ivy |
Libraries | .classpath |
| classpath settings should only be relative and only be adapted if really necessary |