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
When adding a new snapshot test, the tests always seem to pass if no snapshot has been created yet.
E.g. if I add a test case like this:
- it: should do some stuff
set:
deployment:
name: hello
asserts:
- matchSnapshot: {}
running helm unittest ... results in a pass.
So if I change something, e.g.:
- it: should do some stuff
set:
deployment:
name: goodbye
asserts:
- matchSnapshot: {}
the tests still pass.
It's only after I run with -u, and a snapshot is generated, that I can get a test failure.
It seems like a fairly serious bug, as you can get things into production thinking you've not changed your snapshots, but really you have.
Probably the match snapshot func should always fail if no snapshot is found.
The text was updated successfully, but these errors were encountered:
pete-woods
changed the title
Snapshot tests seem to
Snapshot tests always pass before --update is run the first time
Nov 24, 2023
pete-woods
changed the title
Snapshot tests always pass before --update is run the first time
Snapshot tests always pass before --update is run
Nov 24, 2023
(version:
0.3.6
)When adding a new snapshot test, the tests always seem to pass if no snapshot has been created yet.
E.g. if I add a test case like this:
running
helm unittest ...
results in a pass.So if I change something, e.g.:
the tests still pass.
It's only after I run with
-u
, and a snapshot is generated, that I can get a test failure.It seems like a fairly serious bug, as you can get things into production thinking you've not changed your snapshots, but really you have.
Probably the match snapshot func should always fail if no snapshot is found.
The text was updated successfully, but these errors were encountered: