Maintenance: add Idempotency utility to unit tests #1159
Labels
duplicate
This issue is a duplicate of an existing one
idempotency
This item relates to the Idempotency Utility
internal
PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
rejected
This is something we will not be working on. At least, not in the measurable future
Milestone
Summary
Given that #1110 is now merged it's now a good time to add the new utility to the unit testing ran at different points of the dev lifecycle.
Additionally, there were some inconsistencies in the
package.lock
dependencies that prevented some other CI processes from completing successfully (example of failed run).Why is this needed?
To increase confidence in the code to be merged and to prevent regressions.
Which area does this relate to?
Tests, Idempotency
Solution
See linked PR
Acknowledgment
The text was updated successfully, but these errors were encountered: