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
Unit tests in cmd/image-processing, which are written for Ginkgo/Gomega do not run when executed with Ginkgo CLI.
Expected Behavior
Unit tests written for Ginkgo should run fine with the Ginkgo CLI as the driver.
Steps To Reproduce
Clone repo
Run go run github.com/onsi/ginkgo/v2/ginkgo run --coverprofile=unit.coverprofile --output-dir=build/coverage --randomize-all --trace ./cmd/image-processing
Fails with
[FAILED] Unexpected error:
<*fs.PathError | 0x140007dc0c0>:
open : no such file or directory
{
Op: "open",
Path: "",
Err: <syscall.Errno>0x2,
}
occurred
In [It] at: /path/github.ibm.com/coligo/source-to-image/src/build/cmd/image-processing/main_test.go:211 @ 06/12/24 21:25:06.745
Full Stack Trace
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Hey @HeavyWombat , I ran the tests both using go test and Ginko CLI and they both gave me this same error :
[FAILED] Unexpected error:
<*fmt.wrapError | 0xc0007295c0>:
failed to run trivy: exec: "trivy": executable file not found in $PATH
{
msg: "failed to run trivy: exec: \"trivy\": executable file not found in $PATH",
err: <*exec.Error | 0xc0007295a0>{
Name: "trivy",
Err: <*errors.errorString | 0x29c7e50>{
s: "executable file not found in $PATH",
},
},
}
occurred
In [It] at: /home/adarsh/myfiles/OpenSource/Shipwright-io/build/cmd/image-processing/main_test.go:426 @ 07/21/24 23:27:14.619
Also note that i didn't got the above mentioned error (line 211 working correctly), I feel like there's an issue in the test case or code itself, not with the Ginkgo CLI.
Is there an existing issue for this?
Kubernetes Version
n/a
Shipwright Version
Starting with 977a065.
Current Behavior
Unit tests in
cmd/image-processing
, which are written for Ginkgo/Gomega do not run when executed with Ginkgo CLI.Expected Behavior
Unit tests written for Ginkgo should run fine with the Ginkgo CLI as the driver.
Steps To Reproduce
go run github.com/onsi/ginkgo/v2/ginkgo run --coverprofile=unit.coverprofile --output-dir=build/coverage --randomize-all --trace ./cmd/image-processing
Fails with
Anything else?
No response
The text was updated successfully, but these errors were encountered: