This is the third in a series of articles about writing a small reading list app in Go for personal use.

Task is a task runner that aims to be simpler than make.

Task is portable, easy to install, and has slightly better support for skipping tasks when dependencies haven’t changed than mage or goyek.

This is the second in a series of articles about build tools in the Go ecosystem.

Goyek is a simple library for creating build automation in Go.

Goyek’s focus is on simplicity and portability: it lacks sophistication found in other tools. For very simple builds, especially those that are only using Go tools, and that need to be portable across different platforms, Goyek might work for you. For anything even slightly sophisticated, I think there are better options.

In this article I will show how I ported my Makefile to Goyek and provide a brief review of Goyek. I’m going to share some code, but no deep explanations – this is not a Goyek tutorial.

This is the twelfth in a series of articles about writing a small reading list app in Go for personal use.

When I first introduced tests for this app, I showed a strategy of checking for “fragments” in the body of the page – these are just strings, including HTML markup, that the test will verify are present in the generated page.

This approach works, but it’s fragile: trivial changes to a generated page like spaces or newlines can trigger test failures that don’t indicate real bugs in the app. The tests will only be failing because they’re too tightly coupled to the output format.

In this post I’ll show a better way to validate the contents of generated pages using the goquery package.