Setting up E2E tests with MinIO

Oct 13, 2025 by thesweetdesigns.com 12 views

Introduction

In today's fast-paced software development environment, ensuring the quality and reliability of applications is crucial. One of the most effective ways to achieve this is by implementing End-to-End (E2E) tests. These tests simulate real-world user interactions with the application, providing a comprehensive understanding of its functionality and behavior. In this article, we will explore how to set up E2E tests with MinIO, a popular open-source object storage solution.

What are E2E tests?

E2E tests are a type of software testing that simulates real-world user interactions with an application. They cover the entire workflow, from user input to the final output, ensuring that the application behaves as expected. E2E tests are typically automated and run as part of the Continuous Integration/Continuous Deployment (CI/CD) pipeline.

Benefits of E2E tests

Improved quality: E2E tests help identify and fix issues early in the development cycle, reducing the likelihood of bugs and errors.
Increased confidence: By simulating real-world user interactions, E2E tests provide a high level of confidence in the application's functionality and behavior.
Reduced costs: E2E tests can help reduce the cost of debugging and fixing issues by identifying problems early.
Faster development: E2E tests enable developers to quickly identify and fix issues, reducing the time spent on debugging and testing.

Setting up E2E tests with MinIO

To set up E2E tests with MinIO, we will use the following tools:

MinIO: A popular open-source object storage solution.
Go: A modern, statically typed programming language.
Ginkgo: A popular Go testing framework.
Gomega: A popular Go assertion library.

Step 1: Install MinIO

To install MinIO, run the following command:

go get github.com/minio/minio-go/v7

Step 2: Create a MinIO instance

Create a new file called minio.go with the following code:

package main

import (
	"context"
	"fmt"
	"log"

	"github.com/minio/minio-go/v7"
	"github.com/minio/minio-go/v7/pkg/credentials"
)

func main() {
	// Create a new MinIO instance
	minioClient, err := minio.New("localhost:9000", &minio.Options{
		Creds: credentials.NewStaticV4("minioadmin", "minioadmin", ""),
	})
	if err != nil {
		log.Fatal(err)
	}

	// Create a new bucket
	if err := minioClient.MakeBucket(context.Background(), "mybucket", minio.MakeBucketOptions{}); err != nil {
		log.Fatal(err)
	}

	fmt.Println("MinIO instance created successfully")
}

Step 3: Write E2E tests

Create a new file called e2e_test.go with the following code:

package main

import (
	"context"
	"fmt"
	"log"

	"github.com/onsi/ginkgo"
	"github.com/onsi/gomega"
	"github.com/minio/minio-go/v7"
)

var _ = ginkgo.Describe("E2E tests", func() {
	ginkgo.It("should create a new bucket", func() {
		// Create a new MinIO instance
		minioClient, err := minio.New("localhost:9000", &minio.Options{
			Creds: credentials.NewStaticV4("minioadmin", "minioadmin", ""),
		})
		if err != nil {
			log.Fatal(err)
		}

		// Create a new bucket
		if err := minioClient.MakeBucket(context.Background(), "mybucket", minio.MakeBucketOptions{}); err != nil {
			log.Fatal(err)
		}

		// Verify that the bucket was created successfully
		buckets, err := minioClient.ListBuckets(context.Background())
		if err != nil {
			log.Fatal(err)
		}

		gomega.Expect(buckets).To(gomega.HaveLen(1))
		gomega.Expect(buckets[0].Name).To(gomega.Equal("mybucket"))
	})

	ginkgo.It("should upload a file to the bucket", func() {
		// Create a new MinIO instance
		minioClient, err := minio.New("localhost:9000", &minio.Options{
			Creds: credentials.NewStaticV4("minioadmin", "minioadmin", ""),
		})
		if err != nil {
			log.Fatal(err)
		}

		// Create a new bucket
		if err := minioClient.MakeBucket(context.Background(), "mybucket", minio.MakeBucketOptions{}); err != nil {
			log.Fatal(err)
		}

		// Upload a file to the bucket
		if err := minioClient.PutObject(context.Background(), "mybucket", "file.txt", []byte("Hello, World!"), 10, minio.PutObjectOptions{}); err != nil {
			log.Fatal(err)
		}

		// Verify that the file was uploaded successfully
		objs, err := minioClient.ListObjects(context.Background(), "mybucket", &minio.ListObjectsOptions{})
		if err != nil {
			log.Fatal(err)
		}

		gomega.Expect(objs).To(gomega.HaveLen(1))
		gomega.Expect(objs[0].Key).To(gomega.Equal("file.txt"))
	})
})

Step 4: Run E2E tests

To run the E2E tests, use the following command:

go test -v

This will run the E2E tests and report any failures or errors.

Conclusion

In this article, we explored how to set up E2E tests with MinIO. We covered the benefits of E2E tests, the tools required to set them up, and the steps to write and run E2E tests. By following these steps, you can ensure that your application is thoroughly tested and reliable.

Best Practices

Use a testing framework: Use a testing framework like Ginkgo to write and run E2E tests.
Use assertions: Use assertions like Gomega to verify the expected behavior of the application.
Run tests regularly: Run E2E tests regularly as part of the CI/CD pipeline to catch potential issues early.
Use a MinIO instance: Use a MinIO instance to simulate real-world user interactions with the application.

Introduction

In our previous article, we explored how to set up End-to-End (E2E) tests with MinIO. In this article, we will answer some frequently asked questions about setting up E2E tests with MinIO.

Q: What are the benefits of using E2E tests with MinIO?

A: The benefits of using E2E tests with MinIO include:

Improved quality: E2E tests help identify and fix issues early in the development cycle, reducing the likelihood of bugs and errors.
Increased confidence: By simulating real-world user interactions, E2E tests provide a high level of confidence in the application's functionality and behavior.
Reduced costs: E2E tests can help reduce the cost of debugging and fixing issues by identifying problems early.
Faster development: E2E tests enable developers to quickly identify and fix issues, reducing the time spent on debugging and testing.

Q: What are the tools required to set up E2E tests with MinIO?

A: The tools required to set up E2E tests with MinIO include:

MinIO: A popular open-source object storage solution.
Go: A modern, statically typed programming language.
Ginkgo: A popular Go testing framework.
Gomega: A popular Go assertion library.

Q: How do I create a new MinIO instance?

A: To create a new MinIO instance, you can use the following code:

package main

import (
	"context"
	"fmt"
	"log"

	"github.com/minio/minio-go/v7"
	"github.com/minio/minio-go/v7/pkg/credentials"
)

func main() {
	// Create a new MinIO instance
	minioClient, err := minio.New("localhost:9000", &minio.Options{
		Creds: credentials.NewStaticV4("minioadmin", "minioadmin", ""),
	})
	if err != nil {
		log.Fatal(err)
	}

	// Create a new bucket
	if err := minioClient.MakeBucket(context.Background(), "mybucket", minio.MakeBucketOptions{}); err != nil {
		log.Fatal(err)
	}

	fmt.Println("MinIO instance created successfully")
}

Q: How do I write E2E tests with MinIO?

A: To write E2E tests with MinIO, you can use the following code:

package main

import (
	"context"
	"fmt"
	"log"

	"github.com/onsi/ginkgo"
	"github.com/onsi/gomega"
	"github.com/minio/minio-go/v7"
)

var _ = ginkgo.Describe("E2E tests", func() {
	ginkgo.It("should create a new bucket", func() {
		// Create a new MinIO instance
		minioClient, err := minio.New("localhost:9000", &minio.Options{
			Creds: credentials.NewStaticV4("minioadmin", "minioadmin", ""),
		})
		if err != nil {
			log.Fatal(err)
		}

		// Create a new bucket
		if err := minioClient.MakeBucket(context.Background(), "mybucket", minio.MakeBucketOptions{}); err != nil {
			log.Fatal(err)
		}

		// Verify that the bucket was created successfully
		buckets, err := minioClient.ListBuckets(context.Background())
		if err != nil {
			log.Fatal(err)
		}

		gomega.Expect(buckets).To(gomega.HaveLen(1))
		gomega.Expect(buckets[0].Name).To(gomega.Equal("mybucket"))
	})

	ginkgo.It("should upload a file to the bucket", func() {
		// Create a new MinIO instance
		minioClient, err := minio.New("localhost:9000", &minio.Options{
			Creds: credentials.NewStaticV4("minioadmin", "minioadmin", ""),
		})
		if err != nil {
			log.Fatal(err)
		}

		// Create a new bucket
		if err := minioClient.MakeBucket(context.Background(), "mybucket", minio.MakeBucketOptions{}); err != nil {
			log.Fatal(err)
		}

		// Upload a file to the bucket
		if err := minioClient.PutObject(context.Background(), "mybucket", "file.txt", []byte("Hello, World!"), 10, minio.PutObjectOptions{}); err != nil {
			log.Fatal(err)
		}

		// Verify that the file was uploaded successfully
		objs, err := minioClient.ListObjects(context.Background(), "mybucket", &minio.ListObjectsOptions{})
		if err != nil {
			log.Fatal(err)
		}

		gomega.Expect(objs).To(gomega.HaveLen(1))
		gomega.Expect(objs[0].Key).To(gomega.Equal("file.txt"))
	})
})

Q: How do I run E2E tests with MinIO?

A: To run E2E tests with MinIO, you can use the following command:

go test -v

This will run the E2E tests and report any failures or errors.

Q: What are some best practices for setting up E2E tests with MinIO?

A: Some best practices for setting up E2E tests with MinIO include:

Use a testing framework like Ginkgo to write and run E2E tests.
Use assertions like Gomega to verify the expected behavior of the application.
Run tests regularly as part of the CI/CD pipeline to catch potential issues early.
Use a MinIO instance to simulate real-world user interactions with the application.

By following these best practices, you can ensure that your application is thoroughly tested and reliable.