Join me for the final part of the One branch to rule them all guided series! We'll implement a full-fledged CI/CD pipeline, with automated tests, git tagging, Docker image building and pushing, and a deployment to Cloud Run.| too long; automated
A long while ago I - Ryan Wilcox - wrote an article for Toptal on Behavior Driven Development (or BDD). I’ve learned a lot in the years since that article was published, so time for a revisit of the entry (which can no longer be found online). Introduction: What is BDD Behavior Driven Development, from it’s own wiki: BDD aims to bridge the gap…| blog.wilcoxd.com
To decide on how to test your application, you need to compromise on some of these 3 key objectives| Serverless First
My #2 problem with arguing testing pyramids vs honeycombs is the disparate definitions of unit test| martinfowler.com
tl;dr They are often broken in pipelines and that might be because they are broken as a concept. A typical issue in a microservices architecture is ensuring that the integration between services wo…| oooops.dev
I’ve been working on a bunch of longform obligation pieces and while they’re a lot of fun, they’re also steadily driving me insane. So I took a day off to write about all of the kinds of automated testing I know about. I’m defining tests here to be “an independent verification program that, as part of verification, executes the code we want to verify.” This means types are not tests, as they don’t involve execution of the code, and contracts are not tests, because they’re not ...| Hillel Wayne