Skip Navigation LinksHome Page > Forums > SpiraTeam Forums > SpiraTeam Issues & Qu... > Test-bed identification
Hi!We need to run test-cases & test-sets on different test-beds (HW setups).
Are there any 'elegant' way to add the test-bed identification to the test execution which will be inherited by the test-run? So later we can check which test-run was made on a given test-bed. Recently we created 'fake' releases, where the last segment of the version # points to the test-bed. The release can be selected as the test-execution starts. (In case of test sets use the 'schedule' field.) Any better idea?
Thanks!
/Z
Hello Zoltan,
I think it would be better to use a Component - you can simply create a set of custom properties to store the different platform components then (OS, database, browser)
I would recommend logging a support ticket if you need more assistance.
Regards,Victoria -
OK.Thanks. I will take a look.
Thank you so much, Zoltan, for the helpful advice and clear instructions. I will consider creating the Component as you suggested!
You can set environment variables like `TEST_BED=TB01` as part of the execution context. Make sure your testing framework records the environment in logs or reports. For example, Jenkins builds parameters → passes to tests → records automatically.
And if you have any questions, please email or call us at +1 (202) 558-6885
