This document discusses software quality in the DevOps world. It defines code quality as applying processes and practices to ensure the final outcome matches expectations. It recommends using tools and automation for quality, including version control systems, CI servers, code quality scanners, and security analysis tools. Practices like peer reviews, test-driven development, and secure development lifecycles can also increase quality. Quality can be enabled through features like feature flags, circuit breakers, deployment gates, and deployment patterns.

1. The computer says no!
Software quality in the DevOps
world
Matteo Emili
Microsoft MVP – Developer Technologies
matteo.emili@live.com
https://mattvsts.github.io || http://twitter.com/MattVSTS

2. “My code is perfect!”
Yeah… about that.

3. “But it works!”
It might, but how?

4. DevOps is built on top
of the concept of
quality
Even the best craftsmen need a helping hand.

5. Automation is king
You need maximum automation to get the most value

6. Quality needs to be
anywhere
Every step of the way has key areas for quality improvement

7. ‘Quality’ or ‘Code
Quality’?
Two different things indeed…

8. Industry standards
Halstead complexity measures
Cyclomatic complexity
Maintainability index
CERT Secure Coding Standards
CWE List
…
Team-specific choices
Documentation standards
Style rules
Patterns re-use
Code Coverage
Churn rate
…
Let’s define code quality first

9. How about quality?
Quality is all about applying process and practices to ensure
the final outcome matches the expectations

10. Use tools and
automation
Quality is all about applying process and practices to ensure
the final outcome matches the expectations

11. Tools
A modern version control system
CI server
Scripts or extensions for your CI
server
Code quality scanner
Security Vulnerability analysis
tools
…
Practices
Peer reviews
Bug bashes, dedicated spikes
Test-driven Development
Circuit-breakers in the system
Secure Development Lifecycle
…
Reaching the quality bar

12. Demo
Where and how to apply practices to increase quality

13. A word on quality
enablers
Some patterns to enable pervasive quality in your apps

14. Feature flags
App-level segregation to control exposure

15. Circuit breakers
Service segregation to isolate failures

16. Deployment gates
Check system status, run UAT, … before approving a stage

17. Deployment patterns
A deployment is not just dumping bits somewhere – embed
quality checks

18. Tools reference
• SonarQube (https://sonarsource.com)
• Secure DevOps Kit for Azure DevOps
(https://azsk.azurewebsites.net)
• WhiteSource Bolt
(https://marketplace.visualstudio.com/items?itemName=
whitesource.ws-bolt)
• Visual Studio Marketplace
(https://marketplace.visualstudio.com)

19. Thanks!