How much time do agile development teams lose due to shared test environments?

How much time do agile development teams lose due to shared test environments?

Agile development teams often share test environments which is nominally a cost effective solution as test environments are, by their nature, quite expensive to provision. But is this really the most cost and time effective way to provide capability to your testers? Let’s tell a short story here…

How often has a developer run a final test before leaving for the evening to ensure all is well:

ost-shared-env-001

 

A colleague or colleagues check in some change to the test environment or perhaps alter something in the shared test system. This is all quite normal practice and happens everyday:

ost-shared-env-002

 

Our developer returns the next day, makes a small change and runs their tests again. This time they fail:

ost-shared-env-003

The developer will generally assume that their changes have caused the problem and will go searching. This can take many hours or even days before they discover that something else has changed in the shared test environment. This leads to many frustrating and wasted hours of an agile development cycle.

Developer Independence

The software development cycle up until now has been committed to the principle that test environments are complex and expensive to provide and thus can only be shared. In many cases, developers don’t even have access to a test environment using simple stubs to simulate the environment. Often the first time a new or modified application is connected to a test system is when it is passed to the test or even user acceptance team for testing leading to far more bugs being found during testing which are 10 times more expensive to fix than bugs found during development.

ost-shared-env-004

An Agile Testing Sandbox simulates an environment upon which an application is dependent but runs independent of the real environment on Cloud, Docker or commodity hardware and software. Consider a sandbox to be like a flight simulator for your back office environments. The developer develops and tests against a standalone environment to them which reacts exactly like the real environment. Once the sandbox is created, it can be launched as often as required as it is a cost effective solution to the problems caused by shared test environments.

Using agile testing sandboxes changes this paradigm as a sandbox can be provided in a cost effective manner to each developer enabling them to start testing with a simulation of the real environment from day one.

Portus EVS enables the creation of sandbox environments in days thus supporting this new development paradigm and helping organizations to get even more from their agile development teams.

 

Written by : Ostia Solutions