๐งช I built a tiny open-source thing that is probably useful mostly to me, but maybe you have the same workflow pain.
I often need a realistic API for UI prototyping, testing UI frameworks, integration tooling, load-test tooling, and demo apps for talks.
Instead of creating a new backend every time, I built MMLib.DummyApi: โ configurable collections โ working CRUD endpoints (GET/POST/PUT/DELETE) โ dummy seed data โ edge-case simulation (delay, retries, forced errors, chaos, background updates)
So it behaves like a real API quickly, including POST/PUT schema validation.
I wrote a short practical guide here: https://blog.burgyn.online/2026/03/05/mmlib-dummyapi
#dotnet #api #testing #devtools
I built a configurable mock API for my prototypes/tests so I do not need to recreate backend CRUD every time. It supports GET/POST/PUT/DELETE, seed data, and edge-case simulation. https://blog.burgyn.online/2026/03/05/mmlib-dummyapi #dotnet #testing