We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have a test file like:
// +build e2e package e2e import ( "testing" "github.com/sebdah/goldie/v2" ) func TestFoo(t *testing.T) { g := goldie.New(t) out := []byte("some-text") g.Assert(t, "example", out) }
And I am running:
go test -tags=e2e -update -clean ./...
And the output is:
? github.com/myrepo/myproj [no test files]
I would expect it to create the golden file but it does nothing. If I remove the -update flag the the test runs but fails because of no golden file.
-update
Manually creating the golden file does work but I cannot get the -update flag to create the file.
I am using v2.
Any ideas what I am doing wrong?
The text was updated successfully, but these errors were encountered:
@danawoodman I am not sure that -update does not work, but this is solved by adding flags after ./...
./...
Sorry, something went wrong.
I am not sure that -update does not work, but this is solved by adding flags after ./...
Unfortunately, that breaks if you're also testing other packages which don't use goldie:
goldie
$ go test ./... -update flag provided but not defined: -update [...]
Same. Can anyone provide a solution. @sebdah do you have time to investigate?
No branches or pull requests
I have a test file like:
And I am running:
go test -tags=e2e -update -clean ./...
And the output is:
I would expect it to create the golden file but it does nothing. If I remove the
-update
flag the the test runs but fails because of no golden file.Manually creating the golden file does work but I cannot get the
-update
flag to create the file.I am using v2.
Any ideas what I am doing wrong?
The text was updated successfully, but these errors were encountered: