Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Not matcher doesn't provide descriptive output #8

@wfernandes

Description

@wfernandes

When running the following assertion,

Expect(t, fmt.Errorf("some error")).To(Not(HaveOccurred()))

we get the output below

$ go test
--- FAIL: TestSomething (0.00s)
	expect.go:44: match matchers.HaveOccurredMatcher{}
		/Users/wfernandes/workspace/go/src/test/some_test.go:14

match matchers.HaveOccurredMatcher{} is not as useful when it comes to understanding what originally failed. It would be nice to see the failure from the HaveOccurred matcher.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions