3 ms·
We do too, and it is tied into the TDD cycle. Guard will first execute the rspec tests, and only if those pass it will execute rubocop. This way you don't have
by hobofan 12y ago
We do too, and it is tied into the TDD cycle.
Guard will first execute the rspec tests, and only if those pass it will execute rubocop. This way you don't have rubocop immediatelly complaning if you make a style violation and can focus on making the code work first. Once you are done with that you will still nagged about style before you commit your code.
- andreasklinger 12y agoYea we have it the other way round. Usually tests take quite a bit and you dont want to wait forever to finally see an obvious style violation.
- hobofan 12y agoOur tests take < 10secs and after implementing a commit worth of changes (I would say ours are comparatively small) there are usually less than 3 style violations piled up.