Testing

A better way to end-to-end test your webapp

End-to-end tests are the best way to test your webapp, but they're flaky and annoying to write. I'm trying a new agentic approach that fixes the issue.

What I mean by "tests can be slop"

Tests may look like slop, but make them clear, not clever. Best practices are key: Test outcomes, not code. Name with intent. Keep tests independent. More straightforward tests beat fewer abstract ones.

AI writes good tests, actually

I've been using AI to write tests and it works surprisingly well! Here's how.

Why you shouldn't use AI to write your tests

If you derive tests from your implementation, you can't apply the Beyonce rule. What if the code is wrong and that wasn't the programmer's intent? We'll never know. The bug now exists in both places.

pg-mem and jest for smooth integration testing

The cult of TDD leads you down a dark and stormy path towards brittle code with a false sense of security. But there is a better way. A sweet spot between unit and heavy integration.

How to configure Jest with TypeScript

Using plain Jest on a TypeScript codebase is kinda rough. No types in tests no thanks. Making Jest and TypeScript work together smoothly is something you do just rarely enough to forget the details. Hope this helps you and future me too ✌️

How to run JavaScript tests in Chrome on Travis

Bring Ruby VCR to Javascript testing with Capybara and puffing-billy

Unit testing is anti-productive