Engineering Notes
A running log of product decisions behind MockForge, from scenario modeling and test hardening to release safety and client generation tradeoffs.
March 28, 2026
Two weeks of field testing against 66+ proxy targets and real-world specs from GitHub, Amazon S3, and Xero drove multi-target conformance, HAR-to-YAML generation, field-level schema errors, and Swagger 2.0 formData support.
March 8, 2026
Why we treat contract drift as an alerting event and how endpoint-level mismatch metadata shortens triage loops.
March 8, 2026
A practical migration sequence for moving into v0.3 safely: baseline drift, stage strictness, then move critical routes with rollback toggles.
March 7, 2026
How the 0.3.55 to 0.3.57 releases moved MockForge from generic API checks into spec-driven conformance with response schema validation and SARIF output.
March 7, 2026
Spec-driven OpenAPI conformance turns API testing from generic request checks into real contract verification against the features your spec actually uses.
March 7, 2026
A technical deep dive into the 0.3.46 to 0.3.54 security-testing hardening arc across payload delivery, cookie handling, grouped CRS requests, and measured SQLi detection gains.
March 7, 2026
Security benchmarks are only trustworthy when payload delivery is right. What it takes to move from partial coverage to meaningful WAFBench results.
March 7, 2026
A short product update on the 0.3.72 and 0.3.73 releases covering admin startup reliability, clearer failed-check reporting, and more accurate conformance behavior.
March 7, 2026
Small reliability releases matter when they remove first-run friction and make failed checks easier to trust. What the 0.3.72 and 0.3.73 releases improved.
March 5, 2026
A focused review of v0.2.x hardening work: validation defaults, auth-related flow safety, and migration priorities for teams upgrading from earlier versions.
March 3, 2026
Scenario switching helps teams test stateful behavior instead of static happy-path fixtures. This note outlines a practical scenario model and why it improves integration confidence.
January 21, 2026
How we sequence fixes, hardening, and communication so release speed does not become release risk.
December 10, 2025
A practical note on balancing strict schema fidelity with developer velocity in generated clients.
November 5, 2025
Intelligent API synchronization with change detection, TCP protocol mocking, flexible response selection modes, and real webhook execution.
November 5, 2025
Controlled failure profiles expose retry and fallback weaknesses before integration surprises hit teams.
November 4, 2025
Enterprise-grade TLS/HTTPS and mTLS support, built-in tunneling for local development, and completed SDK implementation phases 1 and 2.
November 2, 2025
Complete OAuth2 with PKCE, structured error handling, request/response validation, interceptors, and multiple authentication methods for production-ready API clients.
November 1, 2025
Request body generation fixed across React, Vue, and Svelte. TypeScript required vs optional fields corrected. Comprehensive multi-framework test coverage added.
October 31, 2025
Critical fixes for OpenAPI example extraction, request body parameter generation, and React client generator Handlebars template logic.
October 29, 2025
Generate type-safe API clients for React, Vue, Angular, and Svelte from OpenAPI specs. Unified spec parser, enhanced mock data generation, and browser mobile proxy mode.
October 23, 2025
The first public release of MockForge: AI-powered API mocking for REST, gRPC, GraphQL, WebSockets, and SMTP in a unified Rust framework.
October 22, 2025
Native GraphQL handlers, programmable WebSockets, HTTP scenario switching, capture scrubbing, unified config profiles, and the mockforge-test integration crate.
October 8, 2025
A staged migration path from static fixtures to state-aware scenario switching for better integration confidence.
