The document discusses a simple ASP.NET web application called 'mockingbird' for creating mock APIs, highlighting its use for integration testing, load testing, and generating documentation. It emphasizes the benefits of using mocks to minimize integration roadblocks, improve application profiling during load tests, and document API behavior in microservices architectures. Overall, 'mockingbird' facilitates thorough testing and improves collaboration among teams utilizing the application.

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.