


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

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











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

Goisidealforbeginnersandsuitableforcloudandnetworkservicesduetoitssimplicity,efficiency,andconcurrencyfeatures.1)InstallGofromtheofficialwebsiteandverifywith'goversion'.2)Createandrunyourfirstprogramwith'gorunhello.go'.3)Exploreconcurrencyusinggorout

Golang is suitable for rapid development and concurrent scenarios, and C is suitable for scenarios where extreme performance and low-level control are required. 1) Golang improves performance through garbage collection and concurrency mechanisms, and is suitable for high-concurrency Web service development. 2) C achieves the ultimate performance through manual memory management and compiler optimization, and is suitable for embedded system development.

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

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.

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.

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.
