How to simulate db ping without sqlmock
When developing software, we often encounter situations where we need to simulate database connections for testing. However, sometimes we may not have a tool like sqlmock to help us achieve this goal. So, how should we simulate the ping operation of the database without sqlmock? In this article, PHP editor Youzi will introduce you to a simple and effective method to achieve this goal, allowing you to successfully conduct simulation tests of database connections.
Question content
I would like to understand how to use mock.mock
to refactor my code to simulate db.ping()
. I want to understand this concept without a framework first.
This is the code I want to test:
func Connect() (*sql.DB, error) { db, err := sql.Open("mysql", "root:secret@tcp(s-maria-db)/s_db") if err != nil { return nil, err } for i := 0; i < 60; i++ { // I am hoping to mock this portion if err := db.Ping(); err == nil { break } time.Sleep(time.Second) } return db, nil }
I tried this article on how to simulate a ping command, but that doesn't actually answer the question. If so, I don't understand the solution as it works for my code.
Workaround
You need to use a separate function for ping, and it needs to accept an interface so that you can conditionally pass in the real *sql.db
or simulation. This is because you cannot override methods on a structure.
// connect opens a connection to the database. func connect() (*sql.db, error) { return sql.open("mysql", "root:secret@tcp(s-maria-db)/s_db") } // pinger defines an interface for pinging. type pinger interface { ping() error } // ping attempts to ping the database, trying several times before failing. func ping(p pinger) error { const maxattempts = 60 var err error for i := 0; i < maxattempts; i++ { if err = p.ping(); err == nil { return nil } if i < maxattempts - 1 { time.sleep(time.second) } } return err }
func main() { if err := run(); err != nil { log.fatal(err) } } func run() error { db, err := connect() if err != nil { return fmt.errorf("connecting to db: %w", err) } defer db.close() if err = ping(db); err != nil { return fmt.errorf("pinging db: %w", err) } ... }
type mockDB struct { mock.Mock } func (m *mockDB) Ping() error { args := m.Called() return args.Error(0) } func TestPing(t *testing.T) { db := &mockDB{} db.On("Ping").Return(...) err := Ping(db) ... db.AssertExpectations(t) }
The above is the detailed content of How to simulate db ping without sqlmock. 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.

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

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