XS✔ ◾ Modular Monolith Testing Rule

[danielmackay]

1. What triggered this change? (PBI link, Email Subject, conversation + reason, etc)

https://github.com/SSWConsulting/SSW.SAW.General/issues/2

2. What was changed?

This pull request introduces a new rule for testing strategies in modular monoliths, focusing on unit, integration, and workflow testing. The document outlines best practices and provides guidelines to ensure robust functionality and maintainable code across multiple modules.

Key additions include:

• Metadata and Introduction:

  • Added metadata for SEO and author information.
  • Provided an introduction emphasizing the importance of a strong testing strategy in modular monolith applications.

• Unit Testing:

  • Described the role of unit testing in validating core business rules and domain logic within individual modules.
  • Highlighted the importance of comprehensive unit tests covering typical and edge cases.

• Integration Testing:

  • Emphasized the value of integration testing to verify module interactions and infrastructure dependencies.
  • Suggested strategies for effective integration testing, including avoiding mocks, using real databases, and isolating test infrastructure.

• Workflow Testing:

  • Explained the significance of workflow tests in covering key business flows and simulating real user actions across multiple modules.
  • Advised on designing workflow tests to ensure all modules work together seamlessly. (rules/modular-monolith-testing/rule.mdR1-R70

3. Did you do pair or mob programming (list names)?

No

[github-actions[bot]]

PR Metrics

✔ Thanks for keeping your pull request small. ✔ Thanks for adding tests.		Lines
Product Code	-
Test Code	-
Subtotal	-
Ignored Code	71
Total	71

Metrics computed by PR Metrics. Add it to your Azure DevOps and GitHub PRs!