| Work | https://slashdeploy.com |
| Old Ruby Blog | http://hawkins.io |
| Github | https://github.com/ahawkins |
| TeamCI | https://teamci.co |
| Work | https://slashdeploy.com |
| Old Ruby Blog | http://hawkins.io |
| Github | https://github.com/ahawkins |
| TeamCI | https://teamci.co |
I was recently on the Ruby Testing Podcast where I discussed a slow change in my perspective to testing and what needs testing. I was excited in the interview so I don't think I did the best job explaining myself. So I'm sharing the link to hopefully spark some discussion here: http://www.rubytestingpodcast.com/adam-hawkins.
I may be alone in my experience, but I've not heard anyone else in the Ruby community speaking about such things. I think this approach increases quality and understanding. What do you think?
Me and Adam Hawkins talk about where, what and how to test. Adam brought up some interesting ideas I hadn't thought about before including not only testing your code but testing your deployment pipeline.
Hello all! I'm Adam. You may know me as Adman65 on twitter or from my old ruby blog at http://hawkins.io. I'm still an active member of Ruby community, and more importantly I just love Ruby. It's still my favorite programming language and I'm happy to be around other Ruby enthusiasts. Thank you @james for setting this up.