Looking to move to Continuous Delivery? Worried about the quality of your the code? Helping your developers understand clean-code practices and getting the right testing strategy in place can take a while. What should you do to control the quality of the incoming code till then? This talk shares our experience of using PRRiskAdvisor to gradually educate and influence developers to write better code and also help the code reviewer to be more effective at their reviews.

Every time a developer raises a pull-request, PRRiskAdvisor analyzes the files that were changed and publishes a report on the pull request itself with the overall risk associated with this pull request and also risk associated with each file. It also runs static code analysis using SonarQube and publishes the configured violations as comments on the pull request. This way the reviewer just has to look at the pull request to get a decent idea of what it means to review this pull request. If there are too many violations, then PRRiskAdvisor can also automatically reject the pull request.

By doing this, we saw our developers starting paying more attention to clean code practices and hence the overall quality of the incoming code improved, while we worked on putting the right engineering practices and testing strategy in place.

 
 

Outline/Structure of the Case Study

  • Setting the context - The problem at hand
  • Quick demo of PRRiskAdvisor
  • Deep-dive into how PRRiskAdvisor works
  • Typical challenges & ways to address them
  • Next steps

Learning Outcome

  • Why it's important to have all information about the pull request in one place, on the pull request itself?
  • What kind of data can help the code-reviewer be more effective?
  • How PRRiskAdvisor works and how it can help?

Target Audience

Architects, software engineers, testers, technical leaders and anyone interested in improving code quality.

schedule Submitted 1 year ago

Public Feedback

comment Suggest improvements to the Speaker