You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As noted here, many snapshots throughout the codebase do not have an associated name, and are hence based on line number. If assertions are moved around, then the snapshots will break, which should not happen. We should add names to all snapshot tests.
┆Issue Number: ENG-916
The text was updated successfully, but these errors were encountered:
## Summary
Added names to all snapshot tests which did not have them.
## Background
If a certain test had multiple snapshot assertions, they would be named
based on their ordering. Hence any reordering, removal, or addition of
the snapshots would break the test, which should not be the case. This
change aims to fix this problem as well as establish a best practice of
naming snapshots moving forward.
## Changes
- Added names to all snapshot tests and regenerated all snapshots not
within Conductor (due to code freeze)
## Testing
Passing all tests.
## Related Issues
closes#1656
## Summary
Added names to all snapshot tests which did not have them.
## Background
If a certain test had multiple snapshot assertions, they would be named
based on their ordering. Hence any reordering, removal, or addition of
the snapshots would break the test, which should not be the case. This
change aims to fix this problem as well as establish a best practice of
naming snapshots moving forward.
## Changes
- Added names to all snapshot tests and regenerated all snapshots not
within Conductor (due to code freeze)
## Testing
Passing all tests.
## Related Issues
closes#1656
As noted here, many snapshots throughout the codebase do not have an associated name, and are hence based on line number. If assertions are moved around, then the snapshots will break, which should not happen. We should add names to all snapshot tests.
┆Issue Number: ENG-916
The text was updated successfully, but these errors were encountered: