In the next set of articles, I would like to experiment with how to deploy automatic test environments, that later can be integrated into the build process. This article is going to be a bit out of the ordinary, as I’m going to use it as a plan, a table of content and a status board for experiment. Feel free to bookmark it and visit back to check on the progress. Alternatively, you can subscribe to email notifications on the blog update at the right side of the screen.
Goal
Develop process, to allow Jenkins to automatically deploy test environment, deploy the build on it and start a set of tests.
Creating test environment
-
Create a minimalistic Hyper-V based virtual machine as a base operating system.
-
Cloning of the operating system in PowerShell, so that Jenkins can take over the process.
-
Creating virtual machine groups, so that a complex environment can be deployed as test environment.
-
Configuring Hyper-V virtual network, so that the test environment can be isolated and at the same time necessary machines provided access to allow manual checks on the product.
Provisioning roles for the virtual machines
-
How to install different roles on the virtual machines, so they can step into the functionality as they supposed to be in the test environment. For example, a database server.
-
Different roles
Automatic deployment of build results into the environment
-
Setting up test databases
-
Installing applications
Verifying results
-
Executing tests in the environment
-
Collecting results from the test environment
So far, this is my plan for the system to be built. Stay with me to find out how it will work. If you have any ideas on how each part could be accomplished, please share it in the comments.
You can connect with me on LinkedIn, Twitter or you can register on the blog. Share if you found this article useful or know somebody who would benefit from reading it.
No comments yet.