VMWare Workstation - optimal environment for software testing
I would like to ask a question about using VMWare Workstation when doing software testing.
I tried to look for some answers online, but could not find any best practices for this specific purpose.
I need to test different versions of the software on different versions of Windows, including installation of the software. I would like to set up the working environment in an optimal way (in terms of disk storage, performance, convenience). One more thing to consider is that the VMs should be shared later with the other developers, so that they can grab and clone a specific setup that they need,
At first I tried setting up a clean installation of Windows, then make a full clone of the machine and install version 1 of our software, then make another clone from clean installation and install version 2.
Then I learned about snapshots, which seemed like a convenient and space-saving way to do the same thing in just one VM, having one snapshot for clean Windows installation and a snapshot for each version of the software. An example of this: Example setup
Then I found about the linked clones too, which might be similar to method 1 and save some space too.
So, I would like to know which way I should choose and if there are any gotchas I should be aware of.
P.S. If you have any suggestions for resources, e.g. articles, videos, courses or books about this topic, I'd be glad to hear about them.
virtual-machine vmware vmware-workstation clone
add a comment |
I would like to ask a question about using VMWare Workstation when doing software testing.
I tried to look for some answers online, but could not find any best practices for this specific purpose.
I need to test different versions of the software on different versions of Windows, including installation of the software. I would like to set up the working environment in an optimal way (in terms of disk storage, performance, convenience). One more thing to consider is that the VMs should be shared later with the other developers, so that they can grab and clone a specific setup that they need,
At first I tried setting up a clean installation of Windows, then make a full clone of the machine and install version 1 of our software, then make another clone from clean installation and install version 2.
Then I learned about snapshots, which seemed like a convenient and space-saving way to do the same thing in just one VM, having one snapshot for clean Windows installation and a snapshot for each version of the software. An example of this: Example setup
Then I found about the linked clones too, which might be similar to method 1 and save some space too.
So, I would like to know which way I should choose and if there are any gotchas I should be aware of.
P.S. If you have any suggestions for resources, e.g. articles, videos, courses or books about this topic, I'd be glad to hear about them.
virtual-machine vmware vmware-workstation clone
Which way you choose would depend on your needs. Your biggest gotcha will be Windows licensing and activation...especially if you're trying to share VMs. I've used linked clones in the past, since it saves a lot of setup time and space.
– essjae
Jan 31 at 18:00
add a comment |
I would like to ask a question about using VMWare Workstation when doing software testing.
I tried to look for some answers online, but could not find any best practices for this specific purpose.
I need to test different versions of the software on different versions of Windows, including installation of the software. I would like to set up the working environment in an optimal way (in terms of disk storage, performance, convenience). One more thing to consider is that the VMs should be shared later with the other developers, so that they can grab and clone a specific setup that they need,
At first I tried setting up a clean installation of Windows, then make a full clone of the machine and install version 1 of our software, then make another clone from clean installation and install version 2.
Then I learned about snapshots, which seemed like a convenient and space-saving way to do the same thing in just one VM, having one snapshot for clean Windows installation and a snapshot for each version of the software. An example of this: Example setup
Then I found about the linked clones too, which might be similar to method 1 and save some space too.
So, I would like to know which way I should choose and if there are any gotchas I should be aware of.
P.S. If you have any suggestions for resources, e.g. articles, videos, courses or books about this topic, I'd be glad to hear about them.
virtual-machine vmware vmware-workstation clone
I would like to ask a question about using VMWare Workstation when doing software testing.
I tried to look for some answers online, but could not find any best practices for this specific purpose.
I need to test different versions of the software on different versions of Windows, including installation of the software. I would like to set up the working environment in an optimal way (in terms of disk storage, performance, convenience). One more thing to consider is that the VMs should be shared later with the other developers, so that they can grab and clone a specific setup that they need,
At first I tried setting up a clean installation of Windows, then make a full clone of the machine and install version 1 of our software, then make another clone from clean installation and install version 2.
Then I learned about snapshots, which seemed like a convenient and space-saving way to do the same thing in just one VM, having one snapshot for clean Windows installation and a snapshot for each version of the software. An example of this: Example setup
Then I found about the linked clones too, which might be similar to method 1 and save some space too.
So, I would like to know which way I should choose and if there are any gotchas I should be aware of.
P.S. If you have any suggestions for resources, e.g. articles, videos, courses or books about this topic, I'd be glad to hear about them.
virtual-machine vmware vmware-workstation clone
virtual-machine vmware vmware-workstation clone
asked Jan 31 at 12:22
DonatasDonatas
1
1
Which way you choose would depend on your needs. Your biggest gotcha will be Windows licensing and activation...especially if you're trying to share VMs. I've used linked clones in the past, since it saves a lot of setup time and space.
– essjae
Jan 31 at 18:00
add a comment |
Which way you choose would depend on your needs. Your biggest gotcha will be Windows licensing and activation...especially if you're trying to share VMs. I've used linked clones in the past, since it saves a lot of setup time and space.
– essjae
Jan 31 at 18:00
Which way you choose would depend on your needs. Your biggest gotcha will be Windows licensing and activation...especially if you're trying to share VMs. I've used linked clones in the past, since it saves a lot of setup time and space.
– essjae
Jan 31 at 18:00
Which way you choose would depend on your needs. Your biggest gotcha will be Windows licensing and activation...especially if you're trying to share VMs. I've used linked clones in the past, since it saves a lot of setup time and space.
– essjae
Jan 31 at 18:00
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1400530%2fvmware-workstation-optimal-environment-for-software-testing%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1400530%2fvmware-workstation-optimal-environment-for-software-testing%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Which way you choose would depend on your needs. Your biggest gotcha will be Windows licensing and activation...especially if you're trying to share VMs. I've used linked clones in the past, since it saves a lot of setup time and space.
– essjae
Jan 31 at 18:00