An HTTP mock server for stubbing services and simulating dynamic API responses using ASP.NET Core and C# scripting.
Mockaco is an HTTP mock server that allows developers to stub external services and simulate dynamic API responses. It leverages ASP.NET Core features, built-in fake data generation, and pure C# scripting to create realistic mocks for testing and development. The tool helps teams test API integrations, simulate network conditions, and verify interactions without depending on live backends.
Backend and full-stack developers working in .NET ecosystems who need to mock APIs for integration testing, frontend developers requiring stable backends for UI development, and QA engineers simulating various API behaviors.
Developers choose Mockaco for its seamless integration with ASP.NET Core, the ability to write mock logic in familiar C# scripting, and its comprehensive feature set including delay simulation, fake data generation, and webhook support—all without learning a new language or framework.
🐵 HTTP mock server, useful to stub services and simulate dynamic API responses, leveraging ASP.NET Core features, built-in fake data generation and pure C# scripting
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Enables dynamic mock logic using pure C# scripting, allowing developers to leverage familiar syntax and libraries without learning a new language, as emphasized in the README.
Includes delay simulation, fake data generation, callback support, and state management, making it suitable for realistic API testing scenarios beyond simple stubbing.
Runs on any environment supported by .NET, including Docker containers, ensuring consistent mock server deployment across development and production stages.
Uses JSON-based mock definitions for quick setup, as noted in the README, facilitating version control and easy integration into CI/CD pipelines.
Heavily reliant on .NET and C#, making it impractical for polyglot teams or projects using other technology stacks for mocking needs.
Complex mocks can lead to lengthy JSON files that are harder to maintain compared to code-based mocking approaches, potentially increasing setup time.
Documentation is hosted on a separate site (natenho.github.io/Mockaco), which may risk being less updated or integrated than built-in help, affecting ease of use.