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











Go language performs well in building efficient and scalable systems. Its advantages include: 1. High performance: compiled into machine code, fast running speed; 2. Concurrent programming: simplify multitasking through goroutines and channels; 3. Simplicity: concise syntax, reducing learning and maintenance costs; 4. Cross-platform: supports cross-platform compilation, easy deployment.

Golang is better than C in concurrency, while C is better than Golang in raw speed. 1) Golang achieves efficient concurrency through goroutine and channel, which is suitable for handling a large number of concurrent tasks. 2)C Through compiler optimization and standard library, it provides high performance close to hardware, suitable for applications that require extreme optimization.

Goimpactsdevelopmentpositivelythroughspeed,efficiency,andsimplicity.1)Speed:Gocompilesquicklyandrunsefficiently,idealforlargeprojects.2)Efficiency:Itscomprehensivestandardlibraryreducesexternaldependencies,enhancingdevelopmentefficiency.3)Simplicity:

Golang is better than Python in terms of performance and scalability. 1) Golang's compilation-type characteristics and efficient concurrency model make it perform well in high concurrency scenarios. 2) Python, as an interpreted language, executes slowly, but can optimize performance through tools such as Cython.

Golang and Python each have their own advantages: Golang is suitable for high performance and concurrent programming, while Python is suitable for data science and web development. Golang is known for its concurrency model and efficient performance, while Python is known for its concise syntax and rich library ecosystem.

Golang and C each have their own advantages in performance competitions: 1) Golang is suitable for high concurrency and rapid development, and 2) C provides higher performance and fine-grained control. The selection should be based on project requirements and team technology stack.

The performance differences between Golang and C are mainly reflected in memory management, compilation optimization and runtime efficiency. 1) Golang's garbage collection mechanism is convenient but may affect performance, 2) C's manual memory management and compiler optimization are more efficient in recursive computing.

C is more suitable for scenarios where direct control of hardware resources and high performance optimization is required, while Golang is more suitable for scenarios where rapid development and high concurrency processing are required. 1.C's advantage lies in its close to hardware characteristics and high optimization capabilities, which are suitable for high-performance needs such as game development. 2.Golang's advantage lies in its concise syntax and natural concurrency support, which is suitable for high concurrency service development.
