Process improvements for better quality Nikolay Kolev

Let’s talk about … quality Good specification Good design Good code Good unit & integration tests Good test suite Good management Good development process Good monitoring over quality metrics and development process

Let’s talk about … standards Can we improve the quality by enforcing standards on the development process? Enforcing standards will lead to: Better specification Better design Better code & tests Better management And also to: A little slower development speed A little reduced productivity Some people may get uncomfortable in the beginning

Let’s talk about … Git Stash (Bitbucket) Jenkins SonarQube Continuous Integration “Events” notifications Testing Statistics and monitoring

Git workflow Typical Git workflow and typical build workflow …

Git workflow QA finds a bug in the software and creates a task for a developer to fix it.

Git workflow The developer creates a new branch and works on the bug … … ofcourse he forgets to update bug’s status.

Git workflow The developer creates a pull request, some other guys make a review and the bugfix is merged into the master… … ofcourse he forgets to update bug’s status again.

Git workflow Meanwhile… The QA is wondering what’s going on with his bugfix!?! The bug’s status is still “Open”, but is should have been fixed long time ago… … after a discussion the QA finds out it is ready, but not updated.

Git workflow The build on the test server is ready and the QA starts to retest his bugs … … it seems that the developer broke more functionalities than he fixed.

What we can improve? Add automated tasks management Add automated code quality metrics and code quality gate Add pull request merge hooks and conditions Use continuous integration Add automated launch of unit & other tests Add automated notifications to some people for some events Automate status reports

Improved workflow

Jira improvements Customized tasks workflow Automated task status changes (triggers) Automated notifications Automated tasks creation Development progress information Automated tasks/sprints reports

Code quality improvements Keep your code clean Know your problems early Make sure your code will get merged successfully

Automated builds on branches Unit tests on branches Sonar analysis Code coverage analysis Other checks before marking the branch as successful

Make sure EVERYTHING is meeting your requirements Pull requests improvements Make sure EVERYTHING is meeting your requirements All review comments are going to be fixed Pull request approvals Code meets quality gate conditions and all tests pass All connected jira tasks are in the right status/condition

Spread the word Tell Jenkins to run tests and analysis on the master Tell Jenkins to run a Continuous Integration build Tell sonar to clean branch’s analysis Tell other involved systems or people about the merge

Remote triggers Using SCM changes triggers Jenkins jobs can be triggered by anything

Continuous integration Infrastructure automation Automated tests Test reports Artifacts archiving

Test servers builds Fast builds Guaranteed build quality

Final results Find problems as early as possible (fail fast) All new code is reviewed All new code is tested Almost no chance for broken code in the master Code quality is easy to be reviewed and managed Code quality is improving in time (boy scout rule) Development progress is visible and trackable Jira tasks are updated and trackable Less time is lost in tasks management

Final results Automated reports are sent Repeatable results Everyone interested in some events are notified Faster builds Young developers have more courage

T-shirt anyone?

ANY STIONS?

Thank you! Nikolay Kolev DevOps Engineer Sirma ITT nikolay.kolev@sirma.bg www.qachallengeaccepted.com