Hi, I'm thinking of how to handle multiple machine configurations in SpiraTest. This is the situation: Testcase A must be run on all machine configs: 1, 2 and 3. Testcase B must be run on config 1. It cannot be run on 2 and 3. Testcase C must be run on config 1 and 2. It cannot be run on 3. Whats the best practice here? Is it to create a folder structure for each machine configuration and clone test cases that applies to more than one configuration into those folders? Or is there a way of working with custom fields and list to make this work? I must know before I run the tests what configuration that is going to be tested in that run i.e. I want to test one configuration at a time, not mix them. en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spiratest/best-practices/17.aspxthreadId=17Michael Persson (mippzon@gmail.com) Hi, I'm thinking of how to handle multiple machine configurations in SpiraTest. This is the situation: Testcase A must be run on all machine configs: 1, 2 and 3. Testcase B must be run on config 1. It cannot be run on 2 and 3. Testcase C must be run on config 1 and 2. It cannot be run on 3. Whats the best practice here? Is it to create a folder structure for each machine configuration and clone test cases that applies to more than one configuration into those folders? Or is there a way of working with custom fields and list to make this work? I must know before I run the tests what configuration that is going to be tested in that run i.e. I want to test one configuration at a time, not mix them. Thu, 17 Feb 2011 14:28:19 -05002025-01-05T17:40:03-05:00/Support/Forum/spiratest/best-practices/17.aspxmessageId=20David J (adam.sandman+support@inflectra.com) In general when testing on multiple environments, the approach is to use Test Run and Test Set custom properties: https://www.inflectra.com/Support/Forum/spiratest/best-practices/1.aspx However since you need to specify multiple configurations per test case, it's a bit different. We shall be adding multi-select custom properties in v3.2 of SpiraTest which would allow you to have a list of configurations and then be able to multi-select them. The other option would be to build a test set for each configuration and then add the appropriate test cases to the appropriate test set. Would that work? Thu, 17 Feb 2011 17:14:11 -05002011-02-17T17:14:11-05:00/Support/Forum/spiratest/best-practices/17.aspx#reply20messageId=528John Bayne (john.bayne@iongeo.com) Hi, I am demoing 3.2 and and don't see multi-select custom properties. Are they scheduled for inclusion any forthcoming release? Thu, 26 Apr 2012 13:41:32 -04002012-04-26T13:41:32-04:00/Support/Forum/spiratest/best-practices/17.aspx#reply528messageId=539David J (adam.sandman+support@inflectra.com) The version 3.2 referred to in this older post was broken up into two releases - v3.2 and v4.0. The custom properties change will be in the v4.0 release. Thu, 24 May 2012 09:43:04 -04002012-05-24T09:43:04-04:00/Support/Forum/spiratest/best-practices/17.aspx#reply539messageId=7078David J (adam.sandman+support@inflectra.com) In addition, we have now released TestConfigurations+ as a new SpiraApp that makes testing a set of test cases on multiple machine configurations much easier: You can use Test Configurations and this new SpiraApp to generate a test set that contains all possible test cases and a fine-tuned list of platforms (and other parameters) that it should be executed on. Sun, 05 Jan 2025 17:40:03 -05002025-01-05T17:40:03-05:00/Support/Forum/spiratest/best-practices/17.aspx#reply7078