Carlos Reyna
03/24/2025, 6:49 PMlog.Debug call is executing. What is the work around to get test the log.Debug message and not error from a stack trace message in stderr snapshot?
- name: atmos docs no component 2
enabled: true
snapshot: true
description: "Ensure atmos docs command executes with error component not found."
workdir: "fixtures/scenarios/core/"
command: "atmos"
args:
- "docs"
- "bucket6"
expect:
diff: []
exit_code: 1
stdout:
- "no such file or directory"
stderr:
- "component not found"Carlos Reyna
03/24/2025, 7:08 PMAndriy Knysh (Cloud Posse)
03/24/2025, 7:10 PMlog.SetLevel(log.DebugLevel)
log.SetOutput(os.Stdout). // or StderrAndriy Knysh (Cloud Posse)
03/24/2025, 7:10 PMCarlos Reyna
03/24/2025, 7:11 PMlogs:
file: "/dev/stdout"
level: InfoCarlos Reyna
03/24/2025, 7:12 PMCarlos Reyna
03/24/2025, 7:13 PM- name: atmos docs no component 1
enabled: true
snapshot: falseCarlos Reyna
03/24/2025, 7:50 PMCheck warning on line 78 in cmd/docs.go
Codecov
/ codecov/patch
cmd/docs.go#L78
Added line #L78 was not covered by testsAndriy Knysh (Cloud Posse)
03/24/2025, 7:53 PMCarlos Reyna
03/24/2025, 7:57 PMCarlos Reyna
03/24/2025, 7:57 PMCarlos Reyna
03/24/2025, 7:58 PMCarlos Reyna
03/24/2025, 7:58 PMAndriy Knysh (Cloud Posse)
03/24/2025, 7:59 PMAndriy Knysh (Cloud Posse)
03/24/2025, 7:59 PM