Test registry and matching of handlers by causes

[nolar]

These tests "freeze" the public interface of the library regarding the registries and matching of handlers by causes (i.e. resources-events-fields) — to prevent accidental regressions.

Issue : #13

[zincr]

🤖 zincr found 0 problems , 1 warning

ℹ️ Large Commits
✅ Approvals
✅ Specification
✅ Dependency Licensing

Details on how to resolve are provided below

---

Large Commits

Checks all commits for large additions to a single file. Large commits should be reviewed more carefully for potential copyright and licensing issues

This file contains a substantial change, please review to determine if the change comes from an external source and if there are any copyright or licensing issues to be aware of

• ℹ️ tests/registries/test_decorators.py had +100 lines of code changed in a single commit
  Please review this file to determine the source of this change
• ℹ️ tests/registries/test_handler_matching.py had +100 lines of code changed in a single commit
  Please review this file to determine the source of this change
• ℹ️ tests/registries/test_id_detection.py had +100 lines of code changed in a single commit
  Please review this file to determine the source of this change
   

[samurang87]

what's the use of this test? 🤔

[nolar]

To test that all declared (publicly promised) args are accepted, none of them suddenly change their name, none of them are removed.

But mostly for the properties, the same: none are removed or renamed.

Both the class constructor and its properties are considered as part of the public interfaces. And the tests, by concept, should "freeze" the public promises, and they should not change when the code is changed.

Though, maybe there are some other better approaches to do this (freeze the public interface).