How to use coverage tool in Golang unit testing?
Use the go test -cover command in Go unit testing to measure coverage and specify the -cover or -coverprofile option to generate the results; the -covermode option sets the coverage mode (set, count, or atomic). Practical cases demonstrate how to write tests and generate coverage reports using coverage configuration files and the go tool cover command.
How to use coverage tool to test coverage in Golang unit testing
Coverage tool is very important in unit testing because it Can help you identify untested parts of your code. This is critical to ensure the quality and reliability of your code. In Golang, you can use the go test -cover
command to measure coverage in unit tests.
Install the coverage tool
To use the coverage tool in Golang, you need to install it. You can install it using the following command:
go install golang.org/x/tools/cmd/cover
Measure coverage
To measure the coverage of unit tests, use the go test
command and Specify the -cover
flag. This flag can then accept the following values:
- -cover: Displays coverage results, including uncovered lines, files, and packages.
- -coverprofile=profile.out: Write the coverage results to the specified file. This is useful for further analysis or use with other tools.
-covermode=mode: Set the coverage mode. Acceptable values include:
- #set: Use set mode to report coverage. It will assign a counter to each covered line of code and generate a report after the test is completed.
- count: Use count mode to report coverage. It will assign a boolean value to each covered line of code and generate a report after the test is completed.
- atomic: Report coverage using atomic counting mode. It will assign an int64 counter to each covered line of code and generate a report after the test is completed.
Practical case
The following is a brief example demonstrating how to measure coverage in Golang unit testing:
main.go
package main import ( "fmt" "strconv" ) // Add two numbers func Add(a, b int) int { return a + b } // Convert a string to a number func StrToInt(s string) int { n, err := strconv.Atoi(s) if err != nil { fmt.Println(err.Error()) return 0 } return n }
main_test.go
package main import ( "testing" ) func TestAdd(t *testing.T) { tests := []struct { a int b int want int }{ {1, 2, 3}, {0, 0, 0}, {-1, -1, -2}, } for _, tt := range tests { t.Run(fmt.Sprintf("TestAdd%d_%d", tt.a, tt.b), func(t *testing.T) { if got := Add(tt.a, tt.b); got != tt.want { t.Errorf("Add(%d, %d) = %d, want %d", tt.a, tt.b, got, tt.want) } }) } } func TestStrToInt(t *testing.T) { tests := []struct { s string want int }{ {"1", 1}, {"0", 0}, {"-1", -1}, } for _, tt := range tests { t.Run(fmt.Sprintf("TestStrToInt%s", tt.s), func(t *testing.T) { if got := StrToInt(tt.s); got != tt.want { t.Errorf("StrToInt(%s) = %d, want %d", tt.s, got, tt.want) } }) } } func TestCoverage(t *testing.T) { t.Run("Add", func(t *testing.T) { coverProfile := "add_coverage.out" args := []string{"-test.coverprofile=" + coverProfile, "-test.covermode=set"} cmd := exec.Command("go", "test", args...) if err := cmd.Run(); err != nil { t.Fatalf("Could not run coverage test: %v", err) } }) t.Run("StrToInt", func(t *testing.T) { coverProfile := "str_int_coverage.out" args := []string{"-test.coverprofile=" + coverProfile, "-test.covermode=set"} cmd := exec.Command("go", "test", args...) if err := cmd.Run(); err != nil { t.Fatalf("Could not run coverage test: %v", err) } }) }
Execute the following command at the command line to generate a coverage report:
go test -test.coverprofile=coverage.out
This will create a coverage report in the coverage.out
file. You can view the report using the go tool cover
command:
go tool cover -html=coverage.out
This will open an HTML report in your browser showing the lines of code and files that were not covered.
The above is the detailed content of How to use coverage tool in Golang unit testing?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











Steps for unit testing interfaces and abstract classes in Java: Create a test class for the interface. Create a mock class to implement the interface methods. Use the Mockito library to mock interface methods and write test methods. Abstract class creates a test class. Create a subclass of an abstract class. Write test methods to test the correctness of abstract classes.

PHP unit testing tool analysis: PHPUnit: suitable for large projects, provides comprehensive functionality and is easy to install, but may be verbose and slow. PHPUnitWrapper: suitable for small projects, easy to use, optimized for Lumen/Laravel, but has limited functionality, does not provide code coverage analysis, and has limited community support.

Performance tests evaluate an application's performance under different loads, while unit tests verify the correctness of a single unit of code. Performance testing focuses on measuring response time and throughput, while unit testing focuses on function output and code coverage. Performance tests simulate real-world environments with high load and concurrency, while unit tests run under low load and serial conditions. The goal of performance testing is to identify performance bottlenecks and optimize the application, while the goal of unit testing is to ensure code correctness and robustness.

Table-driven testing simplifies test case writing in Go unit testing by defining inputs and expected outputs through tables. The syntax includes: 1. Define a slice containing the test case structure; 2. Loop through the slice and compare the results with the expected output. In the actual case, a table-driven test was performed on the function of converting string to uppercase, and gotest was used to run the test and the passing result was printed.

Unit testing and integration testing are two different types of Go function testing, used to verify the interaction and integration of a single function or multiple functions respectively. Unit tests only test the basic functionality of a specific function, while integration tests test the interaction between multiple functions and integration with other parts of the application.

It is crucial to design effective unit test cases, adhering to the following principles: atomic, concise, repeatable and unambiguous. The steps include: determining the code to be tested, identifying test scenarios, creating assertions, and writing test methods. The practical case demonstrates the creation of test cases for the max() function, emphasizing the importance of specific test scenarios and assertions. By following these principles and steps, you can improve code quality and stability.

In Go function unit testing, there are two main strategies for error handling: 1. Represent the error as a specific value of the error type, which is used to assert the expected value; 2. Use channels to pass errors to the test function, which is suitable for testing concurrent code. In a practical case, the error value strategy is used to ensure that the function returns 0 for negative input.

How to improve code coverage in PHP unit testing: Use PHPUnit's --coverage-html option to generate a coverage report. Use the setAccessible method to override private methods and properties. Use assertions to override Boolean conditions. Gain additional code coverage insights with code review tools.
