Astro
Astro's API routes (files in src/pages/api/) let you build backend endpoints alongside your frontend pages. They handle HTTP methods, parse request bodies, set cookies, and return JSON — all within the same project. But they need their own testing approach: unit tests for handler logic, integration tests
Testing
JUnit 5 ships with a built-in assertion API. AssertJ is a third-party library that replaces it with a fluent, chainable alternative. Both work. The question is which produces better tests. The Fundamental Difference JUnit assertions are static methods with a fixed signature. AssertJ assertions use method chaining on
Testing
AssertJ is a Java assertion library that replaces the default assertions in JUnit and TestNG with a fluent, chainable API. Instead of assertEquals(expected, actual) you write assertThat(actual).isEqualTo(expected) — readable left to right, with IDE auto-complete guiding you to the right assertion for each type. Why AssertJ
Testing
WebAssembly gives you near-native performance in the browser and on the server, but testing Wasm modules has historically been awkward. AssemblyScript — a TypeScript-like language that compiles to Wasm — changes that by bringing a familiar type system and a purpose-built test runner called as-pect. This post covers
Load Testing
Every "Artillery vs k6 vs JMeter" comparison online has the same "resource usage: Moderate/Low/High" row and no numbers behind it. We got tired of repeating that without evidence, so we built a fixed target server, ran all three tools against it with matched load
Testing
Your checkout page breaks on Tuesday. Nobody on your team notices. You find out on Wednesday morning because a customer emails asking why their card got charged twice and no order showed up. That's the moment most people start looking into automated website testing. Not because they read
Testing
Your checkout page breaks on Tuesday. Nobody on your team notices. You find out on Wednesday morning because a customer emails asking why their card got charged twice and no order showed up. That's the moment most people start looking into automated website testing. Not because they read
Load Testing
A load test that only hits one endpoint tells you how fast that endpoint is. It doesn't tell you how your system behaves when users log in, search for products, add items to a cart, and check out — all at the same time, with realistic delays between actions.
Load Testing
Out of the box, Artillery gives you latency percentiles and status code counts. That's a starting point, but for serious load testing you need custom assertions, metrics that go to your observability stack, and hooks to run custom logic during tests. Artillery's plugin system covers all
Load Testing
Artillery is a load testing tool built for developers. You write YAML, you run a command, you get results. No GUI to learn, no Java heap to tune, no XML to wrestle. If you can write a curl command, you can write an Artillery test. This post covers installation, the
Testing
"Just mock it" is the most common piece of testing advice—and one of the most misused. Mocks and stubs both replace real dependencies in tests, but they have fundamentally different purposes. Using one when you need the other leads to tests that pass while hiding real problems.
Load Testing
Running load tests manually before releases is better than not running them. Running them automatically on every pull request is better still. Blocking a merge when performance regresses is the goal. This post covers integrating Artillery into GitHub Actions and GitLab CI, setting thresholds that actually gate deployments, and strategies