Adam Hawkins

22 Followers
1 Following
12 Posts
Blogger, Writer, Speaker, and Code DJ
Workhttps://slashdeploy.com
Old Ruby Bloghttp://hawkins.io
Githubhttps://github.com/ahawkins
TeamCIhttps://teamci.co
@Hooper I'm happy to help you out. What's challenging you at the moment?
@tom_dalling @josh I believe that's called "synthetic testing." That's another important part of a production test portfolio.
@solnic I read your recent blog post. Seems like you've been having a rough time dude. I'm real happy for you that you've steadied the ship and feel more positive.
@josh @tom_dalling Question is: how far is "outside". In my personal experience, pushing "outside" farther to increase surface area yielded positive results. I also think of this in another way: I keep zooming out/up a layer while I can add regression tests. That's what got me start running tests against build artifacts. I wouldn't have made that leap without containers.
Here's a great article by @tom_dalling on Dependency Injection: https://www.rubypigeon.com/posts/dependency_injection_containers_vs_hardcoded_constants/. I use, and advocate for, the hybrid approach. I don't see a reason for anything else more technically complex that provides the same benefits.
Dependency Injection Containers vs Hard-coded Constants

Dependency injection (DI) is a somewhat contentious topic in the Ruby community.Some argue that DI containers are unnecessary complexity cargo-culted from Ja...

@tuomasj Aye my friend, that's a long dark winter up there. When does the sun come out again, April? I do admit that I really miss Finland, the snow, and occasionally the darkness. That may just be longing for a sauna. How's it going at the new gig?
Welcome @MikeG1 :)

@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?

008 - Adam Hawkins - Where, What and How to Test | The Ruby Testing Podcast

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.

@tuomasj Hey Tuomas! How's it going? Still in Oulu?