Skip to content

Commit 8867397

Browse files
committed
Moving documentation around to limit folder clutter
1 parent 66bb34c commit 8867397

13 files changed

+33
-27
lines changed

docs/ADR/README.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -6,15 +6,14 @@ All the ADRs have been approved and are considered final decisions for the proje
66

77
## General ADRs
88

9-
- [Do We __Really__ Need a New Mocking Framework?](DoWeNeedANewMockingFramework.md) - Deciding whether to build a new mocking framework.
10-
- [Matching Target API in Mock API](MatchingTargetApi.md) - Ensures the mock API closely mirrors the target API.
11-
- [How Strict Should MiniMock Be?](HowStrictShouldMiniMockBe.md) - Deciding how strict the framework should be.
12-
- [No Built-in Assertion Feature](NoBuiltInAssertionFeature.md) - Users choose their preferred assertion framework.
13-
- [No Dependencies to Shared Libraries](NoDependencies.md) - Avoid dependencies on shared libraries.
14-
- [Documentation and Examples](DocumentationAndExamples.md) - Approach to documentation and examples for the framework.
15-
- [Logging and Debugging](LoggingAndDebugging.md) - Approach to logging and debugging within the framework.
16-
- [Allowing Skipping Arguments in Mock Setup](SupportSkippingArguments.md) - Allows skipping arguments in mock setups for flexibility.
17-
- [Creating Mocks](CreatingMocks.md) - Decision on how to create mocks in the framework.
9+
- [Do We __Really__ Need a New Mocking Framework?](general/DoWeNeedANewMockingFramework.md) - Deciding whether to build a new mocking framework.
10+
- [Matching Target API in Mock API](general/MatchingTargetApi.md) - Ensures the mock API closely mirrors the target API.
11+
- [How Strict Should MiniMock Be?](general/HowStrictShouldMiniMockBe.md) - Deciding how strict the framework should be.
12+
- [No Built-in Assertion Feature](general/NoBuiltInAssertionFeature.md) - Users choose their preferred assertion framework.
13+
- [No Dependencies to Shared Libraries](general/NoDependencies.md) - Avoid dependencies on shared libraries.
14+
- [Documentation and Examples](general/DocumentationAndExamples.md) - Approach to documentation and examples for the framework.
15+
- [Logging and Debugging](general/LoggingAndDebugging.md) - Approach to logging and debugging within the framework.
16+
- [Creating Mocks](general/CreatingMocks.md) - Decision on how to create mocks in the framework.
1817

1918
## Feature Specific ADRs
2019

@@ -25,6 +24,7 @@ All the ADRs have been approved and are considered final decisions for the proje
2524
- [Support for Events](feature/SupportForEvents.md) - Decision on supporting events in the mocking framework.
2625
- [Support for Indexers](feature/SupportForIndexers.md) - Decision on supporting indexers in the mocking framework.
2726
- Special cases
27+
- [Allowing Skipping Arguments in Mock Setup](general/SupportSkippingArguments.md) - Allows skipping arguments in mock setups for flexibility.
2828
- [Support for Protected Methods](feature/SupportingProtectedMethods.md) - Decision on whether to support mocking protected methods.
2929
- [Support for Generic Methods (WIP)](feature/SupportForGenericMethods.md) - Decision on supporting generic methods in the mocking framework.
3030
- [Support for Asynchronous Methods (WIP)](feature/SupportForAsynchronousMethods.md) - Handling asynchronous methods in the mocking framework.

docs/ADR/feature/SupportForClassesAndInterfaces.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,13 @@
22

33
## Context
44

5-
In the MiniMock framework, there is a need to determine the scope of support for mocking different types of members. While interfaces are the primary focus due to their flexibility and common usage in dependency injection, there is also a need to support classes to cover a broader range of use cases.
5+
In the MiniMock framework, there is a need to determine the scope of support for mocking different types of members.
6+
While interfaces are the primary focus due to their flexibility and common usage in dependency injection, there is also a need to support classes to cover a broader range of use cases.
67

78
## Decision
89

9-
The MiniMock framework will primarily focus on supporting interfaces but will also include support for classes. This approach ensures that the framework can be used in a wide variety of scenarios, providing flexibility and comprehensive mocking capabilities.
10+
The MiniMock framework will primarily focus on supporting interfaces but will also include support for classes.
11+
This approach ensures that the framework can be used in a wide variety of scenarios, providing flexibility and comprehensive mocking capabilities.
1012

1113
## Consequences
1214

@@ -20,7 +22,6 @@ The MiniMock framework will primarily focus on supporting interfaces but will al
2022

2123
- **Complexity**: Adding support for classes may introduce additional complexity in the framework.
2224
- **Maintenance**: Requires ongoing maintenance to ensure both interfaces and classes are supported effectively.
23-
f mocking scenarios.
2425

2526
---
2627

docs/ADR/feature/SupportForConstructors.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,13 +2,16 @@
22

33
## Context
44

5-
In the MiniMock framework, there is a need to determine the scope of support for mocking constructors. Initially, the framework will support only classes with parameterless constructors. This decision simplifies the initial implementation and allows for a gradual introduction of more complex constructor support.
5+
In the MiniMock framework, there is a need to determine the scope of support for mocking constructors. Initially, the framework will support only classes with parameterless constructors.
6+
This decision simplifies the initial implementation and allows for a gradual introduction of more complex constructor support.
67

78
## Decision
89

9-
The MiniMock framework will initially support mocking only classes with parameterless constructors. A plan for adding support for classes with parameterized constructors is being developed and will be implemented in future iterations.
10+
The MiniMock framework will initially support mocking only classes with parameterless constructors.
11+
A plan for adding support for classes with parameterized constructors is being developed and will be implemented in future iterations.
1012

11-
Since the main focus of the framework is to provide a simple and easy-to-use mocking solution for interfaces and classes, the decision to start with parameterless constructors aligns with this goal. See ADR [Support For Classes and Interfaces](SupportForClassesAndInterfaces.md) for more information.
13+
Since the main focus of the framework is to provide a simple and easy-to-use mocking solution for interfaces and classes,
14+
the decision to start with parameterless constructors aligns with this goal. See ADR [Support For Classes and Interfaces](SupportForClassesAndInterfaces.md) for more information.
1215

1316
## Consequences
1417

docs/ADR/SupportSkippingArguments.md renamed to docs/ADR/feature/SupportSkippingArguments.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,4 +22,4 @@ We will allow the skipping of arguments when setting up mocks for methods. This
2222

2323
---
2424

25-
More ADRs can be found in the [docs/ADR](../ADR/README.md) directory.
25+
More ADRs can be found in the [docs/ADR](../README.md) directory.
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,4 +23,4 @@ Mocks will be created using a mock factory. The mock factory will provide a cent
2323

2424
---
2525

26-
More ADRs can be found in the [docs/ADR](../ADR/README.md) directory.
26+
More ADRs can be found in the [docs/ADR](../README.md) directory.

docs/ADR/DoWeNeedANewMockingFramework.md renamed to docs/ADR/general/DoWeNeedANewMockingFramework.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,4 +25,4 @@ We will develop a new mocking framework, MiniMock, that focuses on providing a m
2525

2626
---
2727

28-
More ADRs can be found in the [docs/ADR](../ADR/README.md) directory.
28+
More ADRs can be found in the [docs/ADR](../README.md) directory.

docs/ADR/DocumentationAndExamples.md renamed to docs/ADR/general/DocumentationAndExamples.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,4 +42,4 @@ Accepted
4242

4343
---
4444

45-
More ADRs can be found in the [docs/ADR](../ADR/README.md) directory.
45+
More ADRs can be found in the [docs/ADR](../README.md) directory.

docs/ADR/HowStrictShouldMiniMockBe.md renamed to docs/ADR/general/HowStrictShouldMiniMockBe.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,4 +23,4 @@ The framework will be strict, throwing exceptions when a member that is not mock
2323

2424
---
2525

26-
More ADRs can be found in the [docs/ADR](../ADR/README.md) directory.
26+
More ADRs can be found in the [docs/ADR](../README.md) directory.
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,4 +32,4 @@ Accepted
3232

3333
---
3434

35-
More ADRs can be found in the [docs/ADR](../ADR/README.md) directory.
35+
More ADRs can be found in the [docs/ADR](../README.md) directory.
Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
# Matching Target API in Mock API
22

3-
When creating a mocking class, the mock API must closely mirror the API of the target being mocked. This ensures that the mock can be used as a drop-in replacement for the target, facilitating seamless testing and reducing the learning curve for developers.
3+
When creating a mocking class, the mock API must closely mirror the API of the target being mocked.
4+
This ensures that the mock can be used as a drop-in replacement for the target, facilitating seamless testing and reducing the learning curve for developers.
45

56
## Decision
67

7-
The mock API should reflect the target API with minimal additional methods. The mock should only include methods that already exist in the target API, ensuring consistency and ease of use.
8+
The mock API should reflect the target API with minimal additional methods.
9+
The mock should only include methods that already exist in the target API, ensuring consistency and ease of use.
810

911
## Status
1012

@@ -23,4 +25,4 @@ Accepted
2325

2426
---
2527

26-
More ADRs can be found in the [docs/ADR](../ADR/README.md) directory.
28+
More ADRs can be found in the [docs/ADR](../README.md) directory.

0 commit comments

Comments
 (0)