Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

fail unit tests if coverage is below certain percentage

Tags:

makefile

go

I make a makefile that executes go test -cover. Is it possible to fail the make unit_tests command if coverage is below X? How would I do that?

like image 888
Aman Avatar asked May 01 '18 16:05

Aman


People also ask

What is the least amount of unit test coverage is required?

Minimum Test Coverage Rate: Keeping it between 60 - 70%. Optimal Test Coverage Rate: Keeping it between 70 - 80%. Overkill Test Coverage Rate: Keeping it between 80 - 100%.

What is the percentage of code coverage must be done by unit tests?

While there is no standard for unit testing, one number often cited in the testing world is 80%. "Eighty percent is what I usually see as the gating standard for code coverage in corporate shops," said Tim Ottinger, a senior consultant at Industrial Logic. "Any higher or lower than that is unusual."

What is the least amount of unit test coverage is required in Salesforce?

Salesforce requires all deployed code have unit tests that test at least 75% of the code.

What do test coverage percentages mean?

In computer science, test coverage is a percentage measure of the degree to which the source code of a program is executed when a particular test suite is run.


1 Answers

You can use TestMain in your test to do that. TestMain can act as a custom entry point to tests, and then you can invoke testing.Coverage() to get access to the coverage stats.

So for example, if you want to fail at anything below 80%, you could add this to one of your package's test files:

func TestMain(m *testing.M) {
    // call flag.Parse() here if TestMain uses flags
    rc := m.Run()

    // rc 0 means we've passed, 
    // and CoverMode will be non empty if run with -cover
    if rc == 0 && testing.CoverMode() != "" {
        c := testing.Coverage()
        if c < 0.8 {
            fmt.Println("Tests passed but coverage failed at", c)
            rc = -1
        }
    }
    os.Exit(rc)
}

Then go test -cover will call this entry point and you'll fail:

PASS
coverage: 63.0% of statements
Tests passed but coverage failed at 0.5862068965517241
exit status 255
FAIL    github.com/xxxx/xxx 0.026s

Notice that the number that testing.Coverage() returns is lower than what the test reports. I've looked at the code and the function calculates its coverage differently than the test's internal reporting. I'm not sure which is more "correct".

like image 112
Not_a_Golfer Avatar answered Sep 22 '22 00:09

Not_a_Golfer