Architecture decision records - How not to get lost in the past
Mockingbird – mock api
1. Mockingbird – Mock api
Simple ASP.NET web application for quickly mocking dependency applications.
By
Sagar Rao
2. Why mock?
• Use mock for integration testing.
• Use mock to profile your application during load testing.
• Use mock to generate documentation for upstream.
3. Integration testing
• Unblock yourself during integration testing if one of the dependency
service is affecting your overall progress.
• Proof your application testing from getting affected due to
maintenance jobs.
• Provide mocking data to gauge and guarantee application behavior
after adding new features.
4. Load testing
• Load testing only your application by mocking dependency behavior.
• Sometimes dependency applications can impose cap limits, and
mocking proof your application from failing load tests.
5. Documentation
• Web api documentation can provide a simple mocking call and
response. Useful in Micro services architectures since many teams
could be using your application.