This PR reorganizes and refactors the component tests into a hierarchy of Features, Rules, and Examples. It also introduces a DSL to create a separation between the specification layer and the automation layer, with the hope of having a test suite that doesn't get in the way when a developer desires to change the implementation details of the system under test.
PoA:
[ ] Distill the specification into a spec file with a hierarchy of features, rules, and examples - Doing
[ ] Reorganize existing component tests into the applicable examples (scenarios) - Pending
[ ] Refactor tests to introduce a DSL - Pending
[ ] Implement examples (tests) that don't have equivalent tests from the component tests - Pending
[ ] Optional: implement the same distilled specification but using the acceptance tests setup (for illustration purposes only) - Pending
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This PR reorganizes and refactors the component tests into a hierarchy of Features, Rules, and Examples. It also introduces a DSL to create a separation between the specification layer and the automation layer, with the hope of having a test suite that doesn't get in the way when a developer desires to change the implementation details of the system under test.
PoA: