Category: Software, containerization

The base concept of testing in isolation is probably clear to developers and DevOps engineers. But in practice, testing in isolation isn’t so straightforward: There are a lot of dependencies in place.

An additional benefit is that you don’t have to change anything in your current DevOps pipelines processes.

Also, if you use your continuous integration (the build stage) to validate and compile your source code and produce an artifact, incorporating isolated testing as part of this process makes the continuous deployment run smoother in the end.

Besides running isolated testing to identify missing dependencies, detect tricky bugs and guarantee a cleaner production migration, you should also consider validating performance and overall design improvements as part of your isolated testing scenarios.

Related Articles