Originally published at: http://www.sitepoint.com/inspecting-php-code-quality-scrutinizer/
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
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.
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.
https://insight.sensiolabs.com/ is free for opensource and $6/month for lite, so I see no reason to leave.
This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.