Closed mistic closed 2 years ago
Pinging @elastic/kibana-core (Team:Core)
We're using the kibana version in the declarations
but not in the snapshot:
We need to replace the snapshot-based assertion with something using the actual version number (or use string interpolation in the snapshot, but that's kinda bad when running with -u
)
Probably just matching the error message to a text instead of a snapshot?
}).rejects.toThrowError(`Migration function for version ${version} threw an error`);
Yup, that was
or use string interpolation in the snapshot, but that's kinda bad when running with -u
It's fine, the issue is that any snapshot update will override the custom string. But we can just be careful about that.
I think we should try to rewrite the test
is superseded by migration errors and does not run if a migration fails
atsrc/core/server/saved_objects/validation/integration_tests/validator.test.ts
to not be dependent on the version of the branch otherwise it implies this file needs to be changed at each version bump.