Flog
Rubycritic
Our great sponsors
- ONLYOFFICE ONLYOFFICE Docs — document collaboration in your environment
- InfluxDB - Access the most powerful time series database as a service
- SonarQube - Static code analysis for 29 languages.
| Flog | Rubycritic | |
|---|---|---|
| 6 | 3 | |
| 843 | 3,162 | |
| 2.1% | 0.4% | |
| 5.0 | 1.3 | |
| about 2 months ago | 16 days ago | |
| Ruby | Ruby | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Flog
-
Flog-Driven Development
What if those justifications weren't enough? What if we needed metrics to give an explanation for our refactoring? Let's use the guidance from a tool called flog to guide our changes.
You point flog to a file, or directory, and it provides you with a score. The higher the score, the more attention you might want to pay to it. As for how flog calculates the number, I'll let flog summarize itself again:
-
Improve Code in Your Ruby Application with RubyCritic
Flog checks how difficult your code is to test. It sets a complexity score for each line of code and sums up the score for each method and class.
-
Gems that can identify churn, complexity, duplication and smells.
flog
- Code Red: The Business Impact of Code Quality
Rubycritic
-
Improve Code in Your Ruby Application with RubyCritic
You should consider using RubyCritic if you want a single place to review code improvements for your project. Including RubyCritic in your development process will certainly reduce the time a development team spends working on technical debts. Most technical debts will be mapped out at development time.
-
Best services and/or gems for automated generation of documentation, unit tests, and useful things of this nature
It's also possible to write unit tests in order to better understand or surface your assumptions about a legacy application. I'd also consider running rubycritic against legacy code, to see where the code smells and other hot spots lie.
-
How to Improve Code Quality on a Ruby on Rails Application
RubyCritic: a gem that wraps around static analysis gems such as Reek, Flay, and Flog to provide a quality report of your Ruby code.
What are some alternatives?
Rubocop - A Ruby static code analyzer and formatter, based on the community Ruby style guide. [Moved to: https://github.com/rubocop/rubocop]
Brakeman - A static analysis security vulnerability scanner for Ruby on Rails applications
Flay - Flay analyzes code for structural similarities. Differences in literal values, variable, class, method names, whitespace, programming style, braces vs do/end, etc are all ignored.
SimpleCov - Code coverage for Ruby with a powerful configuration library and automatic merging of coverage across test suites
Reek - Code smell detector for Ruby
Pronto - Quick automated code review of your changes
MetricFu - A fist full of code metrics
rubocop - A Ruby static code analyzer and formatter, based on the community Ruby style guide.
Traceroute - A Rake task gem that helps you find the unused routes and controller actions for your Rails 3+ app