Architecture Decision Records (ADR)
Architecture Decision Records (ADRs) are documents that capture important architectural decisions made during the development of a MiniMock.
All the ADRs have been approved and are considered final decisions for the project.
General ADRs TL;DR
- Do We Really Need a New Mocking Framework? - Deciding whether to build a new mocking framework.
- Matching Target API in Mock API - Ensures the mock API closely mirrors the target API.
- How Strict Should MiniMock Be? - Deciding how strict the framework should be.
- No Built-in Assertion Feature - Users choose their preferred assertion framework.
- No Dependencies to Shared Libraries - Avoid dependencies on shared libraries.
- Documentation and Examples - Approach to documentation and examples for the framework.
- Logging and Debugging - Approach to logging and debugging within the framework.
Feature Specific ADRs TL;DR
- Support for Classes and Interfaces - How should classes and interfaces be supported.
- Support for Constructors - Decision on supporting constructors in the mocking framework.
- Creating Mocks - Decision on how to create mocks in the framework.
- Support for Methods - Decision on supporting methods in the mocking framework.
- Support for Properties - Decision on supporting properties in the mocking framework.
- Support for Events - Decision on supporting events in the mocking framework.
- Support for Indexers - Decision on supporting indexers in the mocking framework.
Unsupported Features
- Unsupported Features - Decision on which features not to support.