Problem executing main function test in Go
#When editor Xigua of php is developing the Go language, he often encounters problems when executing the main function for testing. This situation may cause the program to not function properly or produce unexpected results. In order to resolve this issue, we need to carefully troubleshoot the possible causes and take appropriate steps to fix the code. This article will introduce some common problems and solutions to help developers better deal with such situations.
Question content
I wrote this test a few months ago and it ran successfully without any errors and the init() function was never executed because I only called it from within the test handler function, but now it fails with the following error:
/usr/local/opt/go/libexec/bin/go tool test2json -t /private/var/folders/wt/fc27nzn51rdbvwvjzkl05hlc0000gs/T/GoLand/___TestHandleRequest_in_next_api_cmd_getAllRawTransportOrders.test -test.v -test.paniconexit0 -test.run ^\QTestHandleRequest\E$ {"level":"fatal","msg":"no configuration found: not set","time":"2023-08-27T22:48:03+05:30"} Process finished with the exit code 1
I know the test is calling the init() function, but why not earlier. Am I missing something to understand here?
init.go
//go:build !test // +build !test package main import ( "crypto/tls" "encoding/json" log "github.com/sirupsen/logrus" "os" "lib/storage/ssm" "next-api/aws/dynamodb" "next-api/cmd/utils" "next-api/config" "next-api/http" ) func init() { // Log as JSON instead of the default ASCII formatter. log.SetFormatter(&log.JSONFormatter{}) // Output to stdout instead of the default stderr // Can be any io.Writer, see below for File example log.SetOutput(os.Stdout) // Only log the warning severity or above. log.SetLevel(log.InfoLevel) var err error paramsRepo := ssm.NewRepository() configID, err := utils.GetEnv("CONFIG_ID") if err != nil { log.Fatal("no configuration found: ", err) } cfg, err = config.Load(configID, paramsRepo) if err != nil { log.Fatal("could not load config: ", err) } urls := http.URLs{} json.Unmarshal([]byte(cfg.MABES.URLs), &urls) // configure mTLS cert, err := tls.X509KeyPair([]byte(cfg.MABES.Certificate), []byte(cfg.MABES.PrivateKey)) if err != nil { log.Fatal("could not create MABES certificate: ", err) } MABES, err = http.NewMABESClient(urls, http.WithTLS(cert)) if err != nil { log.Fatal("could not create sofaClient client.", err) } NEXT = dynamodb.NewRepository(cfg.NEXT.Table) }
main.go
package main import ( "encoding/json" "fmt" "github.com/aws/aws-lambda-go/events" "github.com/aws/aws-lambda-go/lambda" log "github.com/sirupsen/logrus" gohttp "net/http" "next-api/api" "next-api/config" "next-api/errors" "next-api/http" "next-api/http/problem" "next-api/mabes" "next-api/next" ) var ( cfg config.Config MABES mabes.Client NEXT next.Repository ) func main() { lambda.Start(handler) } func handler(request events.APIGatewayProxyRequest) (events.APIGatewayProxyResponse, error) { facilityID := request.PathParameters["facilityID"] if facilityID == "" { return events.APIGatewayProxyResponse{ StatusCode: gohttp.StatusBadRequest, Headers: http.Headers("application/problem+json"), Body: problem.ServerError(fmt.Errorf("missing facilityID parameter")).ToJSONResponse(), }, nil } transportOrders, err := api.GetAllRawTransportOrders(facilityID, request.QueryStringParameters, MABES, NEXT) b, err := json.Marshal(transportOrders) if err != nil { log.Errorln(err) if errors.Is(errors.NEXTRead, err) { return events.APIGatewayProxyResponse{ StatusCode: gohttp.StatusOK, Headers: http.Headers("application/json"), Body: fmt.Sprintf(`{"data":%s}`, string(b)), }, nil } return events.APIGatewayProxyResponse{ StatusCode: gohttp.StatusInternalServerError, Headers: http.Headers("application/problem+json"), Body: problem.ServerError(err).ToJSONResponse(), }, nil } return events.APIGatewayProxyResponse{ StatusCode: gohttp.StatusOK, Headers: http.Headers("application/json"), Body: fmt.Sprintf(`{"data":%s}`, string(b)), }, nil }
main_test.go
package main import ( "github.com/aws/aws-lambda-go/events" "github.com/stretchr/testify/assert" "net/http" "strings" "testing" "time" "next-api/api" "next-api/mabes" "next-api/next" ) func TestHandleRequest(t *testing.T) { t.Run("should return the TransportOrders", func(t *testing.T) { req := events.APIGatewayProxyRequest{ PathParameters: map[string]string{ "facility": "11", }, } timeStamp, _ := time.Parse(time.RFC3339, time.Now().Format(time.RFC3339)) sofa1 := next.SofaTransferModel{} sofa1.Phase = "1" sofa1.PartKey.PartCode = "abcd" sofa1.PartKey.DispatcherFacility = "11" sofa1.PartKey.UsageCode = "01" sofa1.Storage.Number = "00315" sofa1.Shipment.RequestedArrivalDate = timeStamp.String() transportOrders := make([]next.SofaTransferModel, 0) transportOrders = append(transportOrders, sofa1) getAllRawTransportOrdersCalls := 0 api.GetAllRawTransportOrders = func(facilityID string, params map[string]string, MABES mabes.Client, NEXT next.Repository) (next.SofaTransferObjects, error) { getAllRawTransportOrdersCalls++ return transportOrders, nil } // when res, err := handler(req) // then assert.Equal(t, 1, getAllRawTransportOrdersCalls) assert.NoError(t, err) assert.Equal(t, http.StatusOK, res.StatusCode) assert.True(t, strings.Contains(res.Body, transportOrders[0].PartKey.PartCode)) assert.True(t, strings.Contains(res.Body, transportOrders[0].Storage.Number)) }) }
Workaround
The top-level function named
init (all lowercase) is always , and is always in Test before is executed. init
The reason why init
is failing now, even if it wasn't before, seems to be a change in environment; i.e. before
was set, but now it is not set, at least not in the shell where the test is executed. set up.
https://www.php.cn/link/905d8fc4ffb4275a428a84589810f8f4
If you run the go test
command with -tags test
, the build constraints at the top of the init.go
file will be respected, which is // go:build !test
and the file will be omitted from the test build. But by default, there is no "test" build tag, so without the -tags test
parameter, these build constraints will be ignored and the init.go### file will be included in the test build . ### p>
The above is the detailed content of Problem executing main function test in Go. 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



OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

The article discusses writing unit tests in Go, covering best practices, mocking techniques, and tools for efficient test management.

The article explains how to use the pprof tool for analyzing Go performance, including enabling profiling, collecting data, and identifying common bottlenecks like CPU and memory issues.Character count: 159

Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

The article discusses the go fmt command in Go programming, which formats code to adhere to official style guidelines. It highlights the importance of go fmt for maintaining code consistency, readability, and reducing style debates. Best practices fo

This article introduces a variety of methods and tools to monitor PostgreSQL databases under the Debian system, helping you to fully grasp database performance monitoring. 1. Use PostgreSQL to build-in monitoring view PostgreSQL itself provides multiple views for monitoring database activities: pg_stat_activity: displays database activities in real time, including connections, queries, transactions and other information. pg_stat_replication: Monitors replication status, especially suitable for stream replication clusters. pg_stat_database: Provides database statistics, such as database size, transaction commit/rollback times and other key indicators. 2. Use log analysis tool pgBadg

Backend learning path: The exploration journey from front-end to back-end As a back-end beginner who transforms from front-end development, you already have the foundation of nodejs,...
