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
--- FAIL: TestIntegrationHappyPath (0.11s)
ssh_exporter_test.go:154: ./ssh_exporter binary not available, try to run go build first: stat ./ssh_exporter: no such file or directory
If the test suite is going to require the binary it should compile it first.
Having it as separate steps makes it harder to automate.
Not sure if integration tests should even run by default when you just run go test.
The text was updated successfully, but these errors were encountered:
omadawn
changed the title
Unit tests don't stand on their own.
Integration tests don't stand on their own.
Nov 10, 2017
--- FAIL: TestIntegrationHappyPath (0.11s)
ssh_exporter_test.go:154: ./ssh_exporter binary not available, try to run
go build
first: stat ./ssh_exporter: no such file or directoryIf the test suite is going to require the binary it should compile it first.
Having it as separate steps makes it harder to automate.
Not sure if integration tests should even run by default when you just run go test.
The text was updated successfully, but these errors were encountered: