Home Database Mysql Tutorial GOLANG INTEGRATION TEST WITH GIN, GORM, TESTIFY, MYSQL

GOLANG INTEGRATION TEST WITH GIN, GORM, TESTIFY, MYSQL

Oct 18, 2024 pm 02:07 PM

GOLANG INTEGRATION TEST WITH GIN, GORM, TESTIFY, MYSQL

Creating a comprehensive integration test for a Golang application using libraries like Gin, Gorm, Testify, and MySQL (using an in-memory solution) involves setting up a testing environment, defining routes and handlers, and testing them against an actual database (though using MySQL in-memory might require a workaround like using SQLite in in-memory mode for simplicity).

Here’s an example of an integration test setup:

1. Dependencies:

  • Gin: for creating the HTTP server.
  • Gorm: for ORM to interact with the database.
  • Testify: for assertions.
  • SQLite in-memory: acts as a substitute for MySQL during testing.

2. Setup:

  • Define a basic model and Gorm setup.
  • Create HTTP routes and handlers.
  • Write tests using Testify and SQLite as an in-memory database.

Here’s the full example:

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

// main.go

package main

 

import (

    "github.com/gin-gonic/gin"

    "gorm.io/driver/mysql"

    "gorm.io/driver/sqlite"

    "gorm.io/gorm"

    "net/http"

)

 

// User represents a simple user model.

type User struct {

    ID    uint   `gorm:"primaryKey"`

    Name  string `json:"name"`

    Email string `json:"email" gorm:"unique"`

}

 

// SetupRouter initializes the Gin engine with routes.

func SetupRouter(db *gorm.DB) *gin.Engine {

    r := gin.Default()

 

    // Inject the database into the handler

    r.POST("/users", func(c *gin.Context) {

        var user User

        if err := c.ShouldBindJSON(&user); err != nil {

            c.JSON(http.StatusBadRequest, gin.H{"error": err.Error()})

            return

        }

        if err := db.Create(&user).Error; err != nil {

            c.JSON(http.StatusInternalServerError, gin.H{"error": err.Error()})

            return

        }

        c.JSON(http.StatusCreated, user)

    })

 

    r.GET("/users/:id", func(c *gin.Context) {

        var user User

        id := c.Param("id")

        if err := db.First(&user, id).Error; err != nil {

            c.JSON(http.StatusNotFound, gin.H{"error": "User not found"})

            return

        }

        c.JSON(http.StatusOK, user)

    })

 

    return r

}

 

func main() {

    // For production, use MySQL

    dsn := "user:password@tcp(127.0.0.1:3306)/dbname?charset=utf8mb4&parseTime=True&loc=Local"

    db, err := gorm.Open(mysql.Open(dsn), &gorm.Config{})

    if err != nil {

        panic("failed to connect database")

    }

 

    db.AutoMigrate(&User{})

 

    r := SetupRouter(db)

    r.Run(":8080")

}

Copy after login

Integration Test

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

73

74

75

76

77

// main_test.go

package main

 

import (

    "bytes"

    "encoding/json"

    "github.com/stretchr/testify/assert"

    "net/http"

    "net/http/httptest"

    "testing"

 

    "gorm.io/driver/sqlite"

    "gorm.io/gorm"

)

 

// SetupTestDB sets up an in-memory SQLite database for testing.

func SetupTestDB() *gorm.DB {

    db, err := gorm.Open(sqlite.Open(":memory:"), &gorm.Config{})

    if err != nil {

        panic("failed to connect to the test database")

    }

    db.AutoMigrate(&User{})

    return db

}

 

func TestCreateUser(t *testing.T) {

    db := SetupTestDB()

    r := SetupRouter(db)

 

    // Create a new user.

    user := User{Name: "John Doe", Email: "john@example.com"}

    jsonValue, _ := json.Marshal(user)

    req, _ := http.NewRequest("POST", "/users", bytes.NewBuffer(jsonValue))

    req.Header.Set("Content-Type", "application/json")

    w := httptest.NewRecorder()

    r.ServeHTTP(w, req)

 

    assert.Equal(t, http.StatusCreated, w.Code)

 

    var createdUser User

    json.Unmarshal(w.Body.Bytes(), &createdUser)

    assert.Equal(t, "John Doe", createdUser.Name)

    assert.Equal(t, "john@example.com", createdUser.Email)

}

 

func TestGetUser(t *testing.T) {

    db := SetupTestDB()

    r := SetupRouter(db)

 

    // Insert a user into the in-memory database.

    user := User{Name: "Jane Doe", Email: "jane@example.com"}

    db.Create(&user)

 

    // Make a GET request.

    req, _ := http.NewRequest("GET", "/users/1", nil)

    w := httptest.NewRecorder()

    r.ServeHTTP(w, req)

 

    assert.Equal(t, http.StatusOK, w.Code)

 

    var fetchedUser User

    json.Unmarshal(w.Body.Bytes(), &fetchedUser)

    assert.Equal(t, "Jane Doe", fetchedUser.Name)

    assert.Equal(t, "jane@example.com", fetchedUser.Email)

}

 

func TestGetUserNotFound(t *testing.T) {

    db := SetupTestDB()

    r := SetupRouter(db)

 

    // Make a GET request for a non-existent user.

    req, _ := http.NewRequest("GET", "/users/999", nil)

    w := httptest.NewRecorder()

    r.ServeHTTP(w, req)

 

    assert.Equal(t, http.StatusNotFound, w.Code)

}

Copy after login

Explanation

  1. main.go:

    • Defines a User struct and sets up basic CRUD operations using Gin.
    • Uses Gorm for database interactions and auto-migrates the User table.
    • SetupRouter configures HTTP endpoints.
  2. main_test.go:

    • SetupTestDB initializes an in-memory SQLite database for isolated testing.
    • TestCreateUser: Tests the creation of a user.
    • TestGetUser: Tests fetching an existing user.
    • TestGetUserNotFound: Tests fetching a non-existent user.
    • Uses httptest.NewRecorder and http.NewRequest for simulating HTTP requests and responses.
    • Uses Testify for assertions, like checking HTTP status codes and verifying JSON responses.

Running the Tests

To run the tests, use:

1

go test -v

Copy after login

Considerations

  • SQLite for In-memory Testing: This example uses SQLite for in-memory testing as MySQL doesn't natively support an in-memory mode with Gorm. For tests that rely on MySQL-specific features, consider using a Docker-based setup with a MySQL container.
  • Database Migrations: Always ensure the database schema is up-to-date using AutoMigrate in tests.
  • Isolation: Each test function initializes a fresh in-memory database, ensuring tests don't interfere with each other.

The above is the detailed content of GOLANG INTEGRATION TEST WITH GIN, GORM, TESTIFY, MYSQL. For more information, please follow other related articles on the PHP Chinese website!

Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Tools

Notepad++7.3.1

Notepad++7.3.1

Easy-to-use and free code editor

SublimeText3 Chinese version

SublimeText3 Chinese version

Chinese version, very easy to use

Zend Studio 13.0.1

Zend Studio 13.0.1

Powerful PHP integrated development environment

Dreamweaver CS6

Dreamweaver CS6

Visual web development tools

SublimeText3 Mac version

SublimeText3 Mac version

God-level code editing software (SublimeText3)

Hot Topics

Java Tutorial
1657
14
PHP Tutorial
1257
29
C# Tutorial
1230
24
When might a full table scan be faster than using an index in MySQL? When might a full table scan be faster than using an index in MySQL? Apr 09, 2025 am 12:05 AM

Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.

Can I install mysql on Windows 7 Can I install mysql on Windows 7 Apr 08, 2025 pm 03:21 PM

Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.

MySQL: Simple Concepts for Easy Learning MySQL: Simple Concepts for Easy Learning Apr 10, 2025 am 09:29 AM

MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.

Can mysql and mariadb coexist Can mysql and mariadb coexist Apr 08, 2025 pm 02:27 PM

MySQL and MariaDB can coexist, but need to be configured with caution. The key is to allocate different port numbers and data directories to each database, and adjust parameters such as memory allocation and cache size. Connection pooling, application configuration, and version differences also need to be considered and need to be carefully tested and planned to avoid pitfalls. Running two databases simultaneously can cause performance problems in situations where resources are limited.

RDS MySQL integration with Redshift zero ETL RDS MySQL integration with Redshift zero ETL Apr 08, 2025 pm 07:06 PM

Data Integration Simplification: AmazonRDSMySQL and Redshift's zero ETL integration Efficient data integration is at the heart of a data-driven organization. Traditional ETL (extract, convert, load) processes are complex and time-consuming, especially when integrating databases (such as AmazonRDSMySQL) with data warehouses (such as Redshift). However, AWS provides zero ETL integration solutions that have completely changed this situation, providing a simplified, near-real-time solution for data migration from RDSMySQL to Redshift. This article will dive into RDSMySQL zero ETL integration with Redshift, explaining how it works and the advantages it brings to data engineers and developers.

The relationship between mysql user and database The relationship between mysql user and database Apr 08, 2025 pm 07:15 PM

In MySQL database, the relationship between the user and the database is defined by permissions and tables. The user has a username and password to access the database. Permissions are granted through the GRANT command, while the table is created by the CREATE TABLE command. To establish a relationship between a user and a database, you need to create a database, create a user, and then grant permissions.

Laravel Eloquent ORM in Bangla partial model search) Laravel Eloquent ORM in Bangla partial model search) Apr 08, 2025 pm 02:06 PM

LaravelEloquent Model Retrieval: Easily obtaining database data EloquentORM provides a concise and easy-to-understand way to operate the database. This article will introduce various Eloquent model search techniques in detail to help you obtain data from the database efficiently. 1. Get all records. Use the all() method to get all records in the database table: useApp\Models\Post;$posts=Post::all(); This will return a collection. You can access data using foreach loop or other collection methods: foreach($postsas$post){echo$post->

MySQL: The Ease of Data Management for Beginners MySQL: The Ease of Data Management for Beginners Apr 09, 2025 am 12:07 AM

MySQL is suitable for beginners because it is simple to install, powerful and easy to manage data. 1. Simple installation and configuration, suitable for a variety of operating systems. 2. Support basic operations such as creating databases and tables, inserting, querying, updating and deleting data. 3. Provide advanced functions such as JOIN operations and subqueries. 4. Performance can be improved through indexing, query optimization and table partitioning. 5. Support backup, recovery and security measures to ensure data security and consistency.

See all articles