Windows-based developers know that creating test environments for MS applications can be a time-consuming and laborious chore. To make matters worse, traditional test environment methods are often just as frustrating once they’ve been created and used because configuration drift occurs, making the test environment useless.

When a manufacturing company approached Kubisys with these problems, we had a ready solution.

To be precise, this company used Virtual Machines (VMs) to create test environments for their Windows-based environment. Whenever a new test environment needed to be created, there was uncertainty of its accuracy. They kept experiencing delays due to failed service upgrades. They would estimate needing a few days to a week in order to create and validate a test environment, but they once experienced six weeks of downtime because of failed validation.

We’ve witnessed these same kinds of test environment problems when companies fail to invest in faster, more accurate, and more cost-effective methods. But we also understand why companies are hesitant to make the change. Their past experience has taught them:

  • Test environments need ample computing resources.
  • Test environments need trained personnel to use them effectively.
  • Test environments seldom truly reflect production.
  • Test environments are difficult to use due to missing components

At Kubisys, we’ve worked hard to create a new and unique solution to these problems that have plagued developers and QA testers for far too long.

What a Test Environment Can Be

This manufacturing company asked for a Kubisys Platform proof-of-concept use case to be conducted on a QA application. In the past, they hadn’t been able to successfully replicate the application’s servers because the app’s embedded server mappings always wanted to self-correct and point back to the live environment. In other words, when testing this app, it wouldn’t play nice with the other replicated test servers because it wanted to interact with production.

We deployed the Kubisys Platform and replicated the application’s entire environment, which included a standalone SQL server, an application server, a client server, and Active Directory. The company witnessed first-hand how our Platform ensured that the troublesome app wouldn’t self-correct because all of the data it needed or referred to was contained within the Kubisys Test Environment. Moreover no network traffic could leave the bubble even if it wanted to.

Furthermore, because our Platform ensures that production is never affected by created test environments, this company could finally allow secure vendor access to test environments so that patches and upgrades could be applied without company supervision. This freed up many hours for an employee that formerly had to supervise such a time-intensive issue. For instance, one particular fix required 41 hours of working time just so the vendor could replicate the problem.

Finally, the company tested the update on the Kubisys Platform and deployed changes to production. They were surprised with the results: no errors and no downtime. Once they saw how our platform saved them time and prevented errors from being introduced into production, they began to see how they could also quickly and reliably test critical upgrades to their other apps and systems. They reported saving at least 15 hours per month in regard to creating, maintaining and validating test environments.

Now, we’re confident that this company has a different understanding of what a test environment solution can be:

  • Test environments need one resource: the Kubisys Platform.
  • Test environments can be easy to use with minimal training.
  • Test environments always reflect production.
  • Test environments are ready to use in minutes

To schedule a demo or proof-of-concept for your company, contact us at

Share This