-
Notifications
You must be signed in to change notification settings - Fork 0
3 Executing the Tools
This is the third page of the wiki, and will deal with the execution of tools for running code analysis.
This page has been written at the "highly proficient technical manager" level, with the assumptions that they
- "know what Github is"
- "know what code is"
The assumption is that they additionally have
- "a copy of Github Desktop"
- "an updated version of ruby"
- "know how to open their local Terminal in their MacBook and install / execute command-line software"
- "an understanding of basic Linux functions / how to navigate folders"
Additionally, they should have an installation of:
- bundler-audit
- brakeman
- rails-bestpractices
If the previous does not sound like you, maybe you should head to the "Installing the Tools" page.
Care will be taken to provide "plain English" documentation, but without using excessive "nerd English". There will very few pictures in this page, I will show just the first few lines. The complete execution logs will go under "Execution Output"
- Open your terminal and move to the project folder.
- Execute the command
bundle-audit
.
- Open your terminal and move to the project folder.
- Execute the command
brakeman
.
- Open your terminal and move to the project folder.
- Execute the command
rails-best-practices .
.
Per the installation, you should consider checking out the rails-bestpractices site before running the tool (there is a lot of stuff there that just couldn't be included that may apply to your company's code, and certain sections in this project just aren't picked up by it.)