Ptico / flexus

[discontinued] now dry-inflector
MIT License
2 stars 1 forks source link

Reorganise development tools #11

Open Ptico opened 7 years ago

Ptico commented 7 years ago

To involve more people to the development, we need to simplify the contribution process. Here is a plan:

abinoam commented 7 years ago

Yes. I would add that we should fast forward to the latest practices. (as you stated inch for example).

Just a question. If you self assigned it means that you're working on it (coding)? Or just being in charge of coordinating the issue? So to clarify and avoid us colliding and duplicating efforts.

abinoam commented 7 years ago

Mutant has its own task already metrics:mutant

$ rake -T
rake ci                         # Run all specs, metrics and mutant
rake ci:metrics                 # Run metrics (except mutant)
rake metrics:coverage           # Measure code coverage
rake metrics:flay               # Measure code duplication
rake metrics:flog               # Measure code complexity
rake metrics:mutant             # Measure mutation coverage
rake metrics:reek               # Check for code smells
rake metrics:rubocop            # Check with code style guide
rake metrics:yardstick:measure  # Measure docs in  with yardstick
rake metrics:yardstick:verify   # Verify that yardstick coverage is at least 100.0%
rake spec                       # Run all specs
rake spec:integration           # Run integration specs
rake spec:unit                  # Run unit specs
rake yard                       # Generate YARD Documentation
Ptico commented 7 years ago

@abinoam I have some already working code for other projects, so i'll take this for myself

abinoam commented 7 years ago

Great!

mbj commented 7 years ago

The mutant task provided by devtools does suck. I recommend to use a custom one, steal it from my active projects.

This way you can also get incremental mutation testing on CI that speeds up a lot. At the expense of small slippage.