Hello everybody, here we are. The day that I finally tackle CloudFormation. As far as I can remember I always told myself. Even though I…
Back in September, I published a blog post on structuring a Go project in a fairly shallow way but deep enough for anyone to use…
A few weeks ago, I wrote a post on structuring a Golang app but wrote no tests whatsoever for it. All done on purpose, I…
My Musketeers for DotNet Test driven development
Posted in Building future-proof software, and Productivity
Test, four letters, one meaning and for some people a struggle. Getting people around you to write tests is easy only when everyone already agrees with you. As often, there are instances where some people show resistance to writing tests. Here
D: I don’t have time to write tests.
A: I don’t need to test this.
B: I can’t write a test for this.
Simple continuous integration with Appveyor and Newman
Posted in Building future-proof software, Productivity, and Tutorials
Last month, I posted about Postman enabling you to test your APIs with little effort so that you can build future-proof software. Here we are going to cover setting up continuous integration for a simple project by using Newman to run your Postman collections. You may have heard about continuous integration in the past. Most commonly, continuous integration will build software from one’s changes before or after merging them