You should be able to do that with: http://damien.lespiau.name/2017/05/building-and-using-coverage.html
HTH, -- Damien On 18 June 2017 at 17:49, Jérôme LAFORGE <jerome.lafo...@gmail.com> wrote: > Hello, > Can I consider that no workaround? > Thx > > Le dimanche 21 mai 2017 09:48:01 UTC+2, Jérôme LAFORGE a écrit : >> >> Hello, >> I create a classic rest server with mongo database. Some of my tests are >> made like this : >> - at the begining of test, I launch mononDB into docker contener (thx to >> https://github.com/ory/dockertest) >> - I launch my rest server within httptest.Server >> https://golang.org/pkg/net/http/httptest/#Server >> - I create some crafty requests that I run on this and I check the >> response, and the consistency into mongo DB. >> >> The pb is this king of tests are not real unit test, and the go converage >> (I used go convey http://goconvey.co/) doesn't report as it into code >> coverage. >> Mabe the root cause is that not the main test goroutine that execute the >> code? >> >> Do you know a workaround to report this kind of test into go coverage? >> >> Thx in adv. >> Regard >> Jérôme >> > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
