#testcontainers

In today’s fast-paced world of software development, product teams are expected to move quickly: building features, shipping updates, and reacting to user needs in real-time. But moving fast should never mean compromising on quality or security. Thanks to modern tooling, developers can now maintain high standards while accelerating delivery. In a previous article, we explored how Testcontainers…

Photo by ThisisEngineering on Unsplash In this blog post, I will walk you through on how to write integration tests by using Testcontainers when we are building a Spring Boot application that integrates Apache Kafka as a message broker, PostgreSQL for database persistence. Spring Boot introduced great support for Testcontainers, making integration testing simpler and enhancing the ease of local…

Do you need a quick and easy drug test? 

The Abbott SureStep™ Oral Fluid Test Drug Screen Cube is here for you! It tests for six drugs using saliva and gives results in just five minutes. 

Easy to use and accurate, it is great for healthcare professionals. This test is CE-certified and can be stored at 4-30°C. It comes with 25 test containers, 30 saliva collectors, and an instruction manual. 

It is no exaggeration to say that the history of software development is the history of software testing.

Since the advent of software, I am sure you are aware that we, the human race, have been working to improve quality in an effort to make things better.

By the way, when we look back on the history of mankind, we sometimes see the appearance of something that is a paradigm shift. For example, fire, and for example, electricity.

It is clear from history that the level of human culture changed dramatically before and after people learned how to use fire and electricity.

So what exactly is the paradigm shift in software development? What exactly is it that will be the fire and electricity for developers?

That is exactly what a Testcontainers is.

Software testing has long sought to improve efficiency in a variety of ways, and automation efforts have been encouraged. However, software is often affected by external factors, such as services external to the software, such as databases, message broker and etc.

In the past, software developers would work with infrastructure engineers to streamline the preparation of the development environment, for example.

Container technology and Testcontainers have created a paradigm shift that has changed the way software development and testing is done. Software developers themselves can now use databases and other environments as containers from the source code. It creates the environment on demand, when it is needed, and disposes of it neatly when it is no longer needed.

It is truly a Developer Experience itself, isn't it?

I would like to thank you for this wonderful project. I would also like to send my encouragement and support for the further development of this project.

Database Testing Made Simple, Efficient and Fast.

In two earlier articles or blog posts (below and in this article) I argued for producing device tests that goal the databases. I created the situation that tests which run a one SQL statement from a Java backend must be considered device checks. After all, they concentrate on an isolated device of actions and validate often elaborate logic in a different language (SQL). The Java code invoked by…