jeudi 26 avril 2018

Accumulating Go coverage analysis over multiple runs?

It seems the current tooling of go test / go tool cover only allows for recording a single profile of a test suite. This means that currently we cannot account properly for multiple runs of one suite (we're testing concurrent/distributed Go software), are accumulating results of different suites that require different system configurations.

Am I just missing the right way to do it, or are there other tools that I should use to achieve this?

Aucun commentaire:

Enregistrer un commentaire