We had twice the case that context.commit or context.dispatch was called with wrong arguments. Since these methods were mocked in tests, the tests did not these errors.
We should have tests that do not mock context.commit and context.dispatch and ensure that the action or mutation was called with the arguments that _it_ expects.
- We have automated tests (unit or integration) for actions that do not mock the actions/mutations called within, but assert they are called with the arguments they _actually_ expect. These tests must fail when the signature of the called actions/mutations changes.