The course streamlined most common industry level good practices in Financial Institutions for code quality improvement during development and CICD phases.

There are four main sections.

Coding Style Standardization. Explain why it's important to consent the coding style within your team. We will tailor our own style template, and then use this template to enforce the format and style of our code. The tool used in the demo is Checkstyle.

Test Coverage Improvement. Explain what high code coverage means to the team and to the product. we will go through the most popular way of writing unit test and a bit of behaviour test style in action. The tool used in the demo is junit5, mokito, and pact.

Comprehensive Coding Inspection. Explain aspects in coding inspection, the matrix, the process, and tips to fix code smell and other issues to make the code base healthier. The tool used in the demo is Sonarqube server, IntelliJ Sonarlint plugin.

Vulnerability Enhancement. Explain why vulnerability scan is important in Financial Institutions. Start from installing Sonatype Nexus IQ server, to enable IntelliJ plugin to assist rectifying the vulnerability issues. The tool used in the demo is Sonatype Nexus IQ, IntelliJ Nexus IQ plugin.

Java and Maven have been used throughout the demonstration. However, all processes and most of the tools supports other languages and ways of configuration.