5
5
6
6
[ ![ Contributor Covenant] ( https://img.shields.io/badge/Contributor%20Covenant-v1.4%20adopted-ff69b4.svg )] ( CODE_OF_CONDUCT.md ) [ ![ Build Status] ( https://travis-ci.org/fastruby/skunk.svg?branch=master )] ( https://travis-ci.org/fastruby/skunk ) [ ![ Maintainability] ( https://api.codeclimate.com/v1/badges/3e33d701ced16eee2420/maintainability )] ( https://codeclimate.com/github/fastruby/skunk/maintainability ) [ ![ Docs] ( http://img.shields.io/badge/yard-docs-blue.svg )] ( http://rubydoc.info/gems/skunk ) [ ![ codecov] ( https://codecov.io/gh/fastruby/skunk/branch/master/graph/badge.svg )] ( https://codecov.io/gh/fastruby/skunk )
7
7
8
- A RubyCritic extension to calculate StinkScore for a file or project.
8
+ A RubyCritic extension to calculate SkunkScore for a file or project.
9
9
10
- ## What is the StinkScore ?
10
+ ## What is the SkunkScore ?
11
11
12
- The StinkScore is a value that assesses the technical debt of a module. It takes
12
+ The SkunkScore is a value that assesses the technical debt of a module. It takes
13
13
into account:
14
14
15
15
- Code Complexity
16
16
- Code Smells
17
17
- Code Coverage
18
18
19
- The main goal of the StinkScore is to serve as a compass in your next
19
+ The main goal of the SkunkScore is to serve as a compass in your next
20
20
refactoring adventure. It will help you answer these questions:
21
21
22
22
- What can I do to pay off technical debt?
@@ -89,7 +89,7 @@ running simple_cov
89
89
.............
90
90
New critique at file:////Users/etagwerker/Projects/fastruby/skunk/tmp/rubycritic/overview.html
91
91
+-----------------------------------------------------+----------------------------+----------------------------+----------------------------+----------------------------+----------------------------+
92
- | file | stink_score | churn_times_cost | churn | cost | coverage |
92
+ | file | skunk_score | churn_times_cost | churn | cost | coverage |
93
93
+-----------------------------------------------------+----------------------------+----------------------------+----------------------------+----------------------------+----------------------------+
94
94
| lib/skunk/cli/commands/default.rb | 166.44 | 1.6643999999999999 | 3 | 0.5548 | 0 |
95
95
| lib/skunk/cli/application.rb | 139.2 | 1.392 | 3 | 0.46399999999999997 | 0 |
@@ -106,10 +106,10 @@ New critique at file:////Users/etagwerker/Projects/fastruby/skunk/tmp/rubycritic
106
106
| lib/skunk/cli/commands/help.rb | 0.0 | 0.0 | 2 | 0.0 | 0 |
107
107
+-----------------------------------------------------+----------------------------+----------------------------+----------------------------+----------------------------+----------------------------+
108
108
109
- StinkScore Total: 612.31
109
+ SkunkScore Total: 612.31
110
110
Modules Analysed: 13
111
- StinkScore Average: 0.47100769230769230769230769231e2
112
- Worst StinkScore : 166.44 (lib/skunk/cli/commands/default.rb)
111
+ SkunkScore Average: 0.47100769230769230769230769231e2
112
+ Worst SkunkScore : 166.44 (lib/skunk/cli/commands/default.rb)
113
113
```
114
114
115
115
The command will run ` rubycritic ` and it will try to load code coverage data
@@ -125,7 +125,7 @@ Simply run:
125
125
skunk -b <target-branch-name>
126
126
```
127
127
128
- Then get a StinkScore average comparison:
128
+ Then get a SkunkScore average comparison:
129
129
130
130
```
131
131
$ skunk -b master
@@ -159,28 +159,28 @@ running churn
159
159
.................
160
160
running simple_cov
161
161
.................
162
- Base branch (master) average stink score: 290.53999999999996
163
- Feature branch (feature/compare) average stink score: 340.3005882352941
162
+ Base branch (master) average skunk score: 290.53999999999996
163
+ Feature branch (feature/compare) average skunk score: 340.3005882352941
164
164
Score: 340.3
165
165
```
166
166
167
167
This should give you an idea if you're moving in the right direction or not.
168
168
169
169
## Known Issues
170
170
171
- The StinkScore should be calculated per method. This would provide a more accurate
172
- representation of the average StinkScore in a module.
171
+ The SkunkScore should be calculated per method. This would provide a more accurate
172
+ representation of the average SkunkScore in a module.
173
173
174
- I think that the StinkScore of a module should be the average of the StinkScores of
174
+ I think that the SkunkScore of a module should be the average of the SkunkScores of
175
175
all of its methods.
176
176
177
- Right now the StinkScore is calculated using the totals for a module:
177
+ Right now the SkunkScore is calculated using the totals for a module:
178
178
179
179
- Total Code Coverage Percentage per Module
180
180
- Total Churn per Module
181
181
- Total Cost per Module
182
182
183
- For more details, feel free to review and improve this method: [ RubyCritic::AnalysedModule#stink_score ]
183
+ For more details, feel free to review and improve this method: [ RubyCritic::AnalysedModule#skunk_score ]
184
184
185
185
## Development
186
186
0 commit comments