Testing
Bun workspaces let you run tests across every package in a monorepo with a single command. Cross-package imports resolve through the workspace protocol, TypeScript paths work without a build step, and bun test --filter targets packages by name pattern — making the monorepo test loop almost as fast as a
Testing
Object storage tests fall into three tiers: unit tests with mocks (fast, free, no network), integration tests against local emulators (slower, but real behavior), and end-to-end tests against real cloud buckets (slowest, costs money, but catches IAM and CDN issues nothing else will). The key is knowing which
Angular
Angular 19 introduced two major reactive primitives: resource() for async data fetching tied to signals, and linkedSignal() for derived writable state. Both are in developer preview as of Angular 19.0. Testing them requires understanding their async lifecycle — resources go through idle, loading, loaded, error, and local states — and how
Testing
Bun.serve creates HTTP servers in a single function call. Testing them is equally direct: pass a Request object to the same handler function used by the server, or bind to a real port and use Bun's native fetch — no test superagent, no supertest, no http.createServer plumbing.
Testing
Bun ships a native SQLite driver (bun:sqlite) that creates in-memory databases in microseconds. This makes it practical to spin up a fully migrated, seeded database in beforeEach, run tests against real SQL, and discard the database after — no mocking, no Docker, no external process. Key Takeaways In-memory
Testing
S3 multipart upload is a three-phase protocol: initiate (get an upload ID), upload parts (minimum 5MB each), and complete (assemble the parts). Testing it requires verifying each phase independently, handling aborts, and testing resumable upload state management. moto supports multipart upload end-to-end. Key Takeaways Multipart upload is
Angular
Angular 15 introduced provideHttpClient() as a functional alternative to HttpClientModule. Angular 18 completed the migration story with provideHttpClientTesting() — the functional equivalent of HttpClientTestingModule. This guide covers how to test HTTP requests, intercept calls, simulate errors, and mock responses in standalone Angular apps. Key Takeaways Replace HttpClientTestingModule with provideHttpClientTesting(). In standalone
Testing
Stripe provides a rich test environment with special test card numbers, a CLI for webhook simulation, and a test mode API. This guide covers unit testing with mocks, integration testing against the Stripe API, and webhook testing with the Stripe CLI. Stripe Testing Overview Stripe's testing infrastructure is
Testing
Bun ships a built-in test runner (bun:test) that is Jest-compatible by design. It runs TypeScript natively, starts in milliseconds, and covers the full testing surface — matchers, snapshots, mocks, module mocking, and watch mode — without any additional dependencies. Key Takeaways bun:test is Jest-compatible. Most Jest tests
Testing
Azure Blob Storage has two testing paths: Azurite for integration tests against a real local emulator, and azure-storage-blob mocks for fast unit tests. Both have sharp edges — Azurite doesn't support all Blob Storage features, and the official SDK's mock story is weaker than AWS&
Angular
Angular 17 introduced deferrable views — the @defer block that lazily loads components based on triggers like viewport intersection, idle time, user interaction, or explicit programmatic control. Testing deferrable views requires Angular's DeferBlockBehavior and getDeferBlocks() API to control when and how deferred blocks load. Key Takeaways Use DeferBlockBehavior.Manual
Testing
Apache Iceberg tables support schema evolution, partition spec changes, time-travel queries, and row-level deletes — all of which are correctness-critical operations that are easy to break silently. This guide covers testing each of these operations using PyIceberg and a local catalog, verifying that column additions don't