Inspecting PHP Code Quality with Scrutinizer

Originally published at:

We’ve gone through a decent number of tutorials about code quality, inspections, auto-build systems and so on here at SitePoint:

In this article, we’ll take a look at Scrutinizer CI – a continuous integration tool that’s quite expensive and closed to private projects, but very handy for public ones.

Scrutinizer vs/+ Travis

Scrutinizer is kind of like your online version of Jenkins and the tools suggested in the 4-part series mentioned in the introduction of this post. It supports PHP, Ruby, Python and to an extent JavaScript out of the box.

Continue reading this article on SitePoint

I’m using it since january. Thanks to it, I’ve improved the way I’m coding a lot.Your article only cover the most obvious things, there are tons of other useful things.

As for the 19€ pricing, that’s because they recently changed the way they price the licenses. Before, you had a Solo license, costing 19€, where you had access to everything, but could only have 1 private repo. That’s the plan I’m currently subscribed to.

At first, I was kinda upset too by they way they manage complexity and conditions in the analysis. But in the end, I managed to respect these analysis, and I have better code. But I had to refactor a lot.

In fact, I’m getting 10, with a lot of strict coding standards in place. Code is clean, readable, commented, without any bugs.

1 Like

Scrutinizer is nice but far too expensive to worth considering for individuals. $50/month just for Code Smells, Best Practices, Bug Detection,Running Tests and Code Coverage, all of which isn’t that hard to have set/running in an IDE/locally. is free for opensource and $6/month for lite, so I see no reason to leave.

1 Like

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.