


gomock provides missing calls for all submethods except the first one in the main method
php Xiaobian Strawberry introduces gomock to you, which is a powerful testing tool that can provide missing calls for all sub-methods in the main method except the first one. This means that you can use gomock to simulate the behavior of submethods to better test the functionality of the main method. Gomock is very simple to use, making it easy to create and configure mock objects and set expected call and return values. Whether you are in unit testing or integration testing, gomock can help you test and verify better. Whether you are a beginner or an experienced developer, gomock is an excellent tool worth exploring and using.
Question content
I have a go method that is responsible for sending OTP messages to users. It calls four internal methods (I'm talking about sub-methods) RemoveOTP, GetOneTimePassCode, SaveOTP and SendOTP.
File name: user_usecase.go
func (u *UserUseCase) SendUserOTP(ctx context.Context, user *domain.User, mobileNumber string) error { var err error var OTPNumber string var expiration time.Time //Remove previous OTP if any in DB if err = u.Repo.RemoveOTP(ctx, user.ID, mobileNumber); err != nil { return err } //Generate OTP OTPNumber, expiration, err = u.TokenService.GetOneTimePassCode() if err != nil { return err } //Save Code in Database and then send otpDataInput := domain.UserMobileOtps{ UserID: user.ID, MobileNumber: mobileNumber, Email: user.Email, OtpCode: OTPNumber, ExpiredAt: expiration, } if err = u.Repo.SaveOTP(ctx, otpDataInput); err != nil { return err } if err = u.SMSService.SendOTP(ctx, mobileNumber, OTPNumber); err != nil { return err } return nil }
Test case file: user_usecase_test.go and unit test case error method
// setup initializes common variables and returns them. func setup(t *testing.T) (context.Context, *gomock.Controller, *mocks.MockUserRepository, usecase.UserUseCase, domain.User, *mocks.MockTokenService, *mocks.MockSMSService, ) { ctx := context.Background() ctrl := gomock.NewController(t) mockRepo := mocks.NewMockUserRepository(ctrl) mockTokenService := mocks.NewMockTokenService(ctrl) mockSmsService := mocks.NewMockSMSService(ctrl) uc := usecase.UserUseCase{Repo: mockRepo, TokenService: mockTokenService, SMSService: mockSmsService} user := domain.User{ID: 1} return ctx, ctrl, mockRepo, uc, user, mockTokenService, mockSmsService } func TestSendUserOTP_Error(t *testing.T) { ctx, ctrl, mockRepo, uc, user, mockTokenService, mockSmsService := setup(t) otpExpiration := time.Now().Add(time.Minute * 5) defer ctrl.Finish() someError := errors.New("some issue") mockRepo.EXPECT().RemoveOTP(ctx, user.ID, "XXXXXYYYYY").Return(someError).Times(1) mockTokenService.EXPECT().GetOneTimePassCode().Return("XXXYYY", otpExpiration, someError).Times(1) mockRepo.EXPECT().SaveOTP(ctx, domain.UserMobileOtps{UserID: user.ID, MobileNumber: "XXXXXYYYYY", Email: user.Email, OtpCode: "XXXYYY", ExpiredAt: otpExpiration}).Return(someError).Times(1) mockSmsService.EXPECT().SendOTP(ctx, "XXXXXYYYYY", "XXXYYY").Return(someError).Times(1) err := uc.SendVerificationOTP(ctx, &user, "XXXXXYYYYY") assert.Error(t, err) assert.Equal(t, someError, err) }
Now while executing the test case, it does not throw any error for RemoveOTP but gives the remaining three methods. This is the exact error
TestSendUserOTP_Error controller.go:310: missing call(s) to *mocks.MockTokenService.GetOneTimePassCode() /project_path/user/usecase/user_usecase_test.go controller.go:310: missing call(s) to *mocks.MockUserRepository.SaveOTP(is equal to context.Background (*context.emptyCtx), is equal to {{0 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC {0001-01-01 00:00:00 +0000 UTC false}} 0 4 XXXXXYYYYY XXXYYY 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC {2023-10-06 10:34:25.951558924 +0530 IST m=+600.001514851 true} {0001-01-01 00:00:00 +0000 UTC false}} /project_path/user/usecase/user_usecase_test.go controller.go:310: missing call(s) to *mocks.MockSMSService.SendOTP(is equal to context.Background (*context.emptyCtx), is equal to XXXXXYYYYY (string), is equal to XXXYYY (string)) /project_path/user/usecase/user_usecase_test.go controller.go:310: aborting test due to missing call(s) --- FAIL: TestSendUserOTP_Error (0.00s)
I don't want to use a solution like AnyTimes() because I'm sure all submethods will be called once. What would be the ideal solution to this? Please make suggestions.
Workaround
The problem is that your RemoveOTP() function returns an error, so your code does not execute any other method. (As the name suggests, missed calls)
Give AnyTimes() to run successfully, as it can run 0 to many times.
If you really want to test that all methods are executed once, maybe you can mock all functions without returning an error so that it executes all your code
The above is the detailed content of gomock provides missing calls for all submethods except the first one in the main method. 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

AI Hentai Generator
Generate AI Hentai for free.

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 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

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

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

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 article discusses managing Go module dependencies via go.mod, covering specification, updates, and conflict resolution. It emphasizes best practices like semantic versioning and regular updates.

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,...

The article discusses using table-driven tests in Go, a method that uses a table of test cases to test functions with multiple inputs and outcomes. It highlights benefits like improved readability, reduced duplication, scalability, consistency, and a
