Or, you could just add a code coverage tool like SimpleCov or similar. > On 31 Dec 2015, at 6:48 PM, Nigel Sheridan-Smith <[email protected]> wrote: > > Hi Tom, > > One approach is to ensure that all commits have tests within the same commit > as the relevant change. Then depending on your CI/CD process, you can either > provide alerts on coverage levels, or even still prevent further deployment > if your coverage falls below a particular level or if any of your tests fail. > > I have a pre-deployment checklist that must be (virtually) completed before > anything goes into production on one project. e.g. something like > 1. Tests written and pass on dev machine > 2. Tests pass in CI environment > 3. Explicitly manually tested in staging environment against the specific > bugs or changes made > 4. Full end-to-end integration tests pass in CI environment > 5. Coverage is at x% level (C0, C1) [1] > 6. Fixtures, factories, migrations, gem dependencies, tags, branches all > updated and merged; configuration changes to deployment tools > 7. Rubocop offences fixed on changed files, or exceptions made, or > configuration updated > 8. Refactoring where required > 9. Documentation is up-to-date > 10. Business owner is notified of maintenance window > etc etc > > Of course, if you are more 'CD' than 'maintenance window' in your workflow > then you can automate a fair amount of these checks too. > > Cheers, > Nigel > > [1] http://grosser.it/2008/04/04/whats-my-coverage-c0-c1-c2-c3-path-coverage/ > > > > Dr Nigel Sheridan-Smith PhD / Principal > Green Shores Digital > > > > M: +61 403 930 963 > E: [email protected] > W: http://www.greenshoresdigital.com > > > > >> On Wed, Dec 30, 2015 at 7:45 PM, Tom Hale <[email protected]> wrote: >> Hi all, >> >> In the project I'm working on, I'm noticing methods creeping in during >> refactoring that aren't covered in the specs. >> >> What workflows, practices and/or tools do you use to ensure that all methods >> have a spec? >> >> Merry New Year and Happy Christmas :) >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby or Rails Oceania" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/rails-oceania. >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/rails-oceania. > For more options, visit https://groups.google.com/d/optout.
-- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/rails-oceania. For more options, visit https://groups.google.com/d/optout.
