## How to Achieve 100% Coverage in Functional Tests Despite Blind Spots?

Showing Coverage of Functional Tests Without Blind Spots

Problem

In the provided code, the exit method includes a condition that excludes the os.Exit(code) line from coverage results. This creates a blind spot in the coverage report, as the line is executed but not shown as green.

Solution

There are two main approaches to address this issue:

Using TestMain:

• Extract application functionality into separate classes for testing, avoiding the main function.
• Utilize the TestMain function in the testing framework to control the execution of code on the main thread.

Refactoring the Code:

• Remove the if condition from the exit method and use a different mechanism (e.g., a separate thread or a watchdog process) to terminate the process after the coverage profile is written.
• Exclude the main.go file from testing using build tags (e.g., // build !test). This approach is recommended if the main function is simple and does not require testing.

Implementation Example

Here's an updated version of the code using build tags:

<code class="go">//+build !test

package main

import "os"

func main() {
    os.Exit(doFunc())
}</code>

This modified code will be excluded from coverage reports, allowing you to accurately represent the coverage of your functional tests.

Running the Tests

Build the coverage binary with:

<code class="sh">go test -c -coverpkg=. -o example -tags test</code>

Run the tests with:

<code class="sh">./example -test.coverprofile=/tmp/profile</code>

The resulting coverage report should now show 100% statement coverage, including the previously excluded line in the exit method.

The above is the detailed content of ## How to Achieve 100% Coverage in Functional Tests Despite Blind Spots?. For more information, please follow other related articles on the PHP Chinese website!