| 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 |
@tom_dalling Thanks for your feedback. I've not read that book, perhaps I should. I like your phrase "proper end-to-end tests". The tests I'm talking about are definitely end-to-end.
I'd like to encourage people to run e2e tests against their build artifacts. That thought model is on Ruby because there's no traditional artifact. However Docker changed this. Built your docker image with your code. Start a container and run some basic e2e tests agains it. Your deployment pipeline will thank you.
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.