Ginkgo panic when there is un handled error and skips next assertion

[aneeshkp]

I think using Gomega assertions (Expect(...).To(...)) but do not use Ginkgo , causes this error.
This is hard to debug.

Panic is handled when using Ginkgo and Gomega together. The assertions are in It() or Specify() blocks and Ginkgo catches the panic()s and produces useful output.

https://onsi.github.io/ginkgo/#adding-specs-to-a-suite

[aneeshkp]

I was able to catch those errors by adding the following functions into ginkgo tests, The panic is caused Since the go functions are not handling errors.

defer func() {
		// recover from panic if one occured. Set err to nil otherwise.
		if recover() != nil {
			err := errors.New("testNetworkConnectivity panic ")
			log.Error(err)
		}
	}()

[aneeshkp]

This where it fails
Expected
<*json.SyntaxError | 0xc00000ebe0>: {
msg: "unexpected end of JSON input",
Offset: 0,
}
to be nil

  /go/src/github.com/redhat-nfvpe/test-network-function/test-network-function/generic/generic_cnf_tests.go:149