Git configs for excluding whatever testing stuff we don't want to track
OTHERS?? - I need expert advice here <<=======
Where to start? Avoiding the TDD or DDT debate, objective advice on how to get started writing tests which add the most value (but don't overwhelm) will be super valuable. Thoughts:
Follow the "Learn Enough..." (Michael Hartl) convention of trivial controller & model tests to ease into the habit?
Beyond that, best practices for maximizing the ROI of building tests
EXPERT ADVICE NEEDED HERE
Example App - This may be just the way my brain works, but I have found that a real working app which evolves along with the material is a great way to make the concepts sink in.
Additional recommendations welcome.
Although pretty noobish in the Rails world, I have been in software development for 30+ years. My rusty hands-on skills prevent me from defining the best practices in this domain, but I am happy to do the grunt work to create the content (and the sample app) guided by Rails experts here.
IMHO, if this is BetterMinitest, we should include (probably several) "best practices" topics.
Since we are just starting out, I suggest a Start Strong (getting started best practices) set of recommendations, like:
Recommended environment configuration (Guard, Minitest Reporters, etc.)
gem 'minitest-reporters'gem 'guard'andgem 'guard-minitest'Where to start? Avoiding the TDD or DDT debate, objective advice on how to get started writing tests which add the most value (but don't overwhelm) will be super valuable. Thoughts:
Example App - This may be just the way my brain works, but I have found that a real working app which evolves along with the material is a great way to make the concepts sink in.
Additional recommendations welcome.
Although pretty noobish in the Rails world, I have been in software development for 30+ years. My rusty hands-on skills prevent me from defining the best practices in this domain, but I am happy to do the grunt work to create the content (and the sample app) guided by Rails experts here.