<rss version="2.0" xmlns:a10="http://www.w3.org/2005/Atom"><channel><title>Inflectra Customer Forums: Test-bed identification (Thread)</title><description> Hi! We need to run test-cases &amp; 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 </description><language>en-US</language><copyright>(C) Copyright 2006-2026 Inflectra Corporation.</copyright><managingEditor>support@inflectra.com</managingEditor><category domain="http://www.dmoz.org">/Computers/Software/Project_Management/</category><category domain="http://www.dmoz.org">/Computers/Software/Quality_Assurance/</category><generator>KronoDesk</generator><a10:contributor><a10:email>support@inflectra.com</a10:email></a10:contributor><a10:id>http://www.inflectra.com/kronodesk/forums/threads</a10:id><ttl>120</ttl><link>/Support/Forum/spirateam/issues-questions/3030.aspx</link><item><guid isPermaLink="false">threadId=3030</guid><author>Zoltan Borbas (zoltan.borbas@harptechnologies.com)</author><title>Test-bed identification</title><description> Hi! We need to run test-cases &amp; 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 </description><pubDate>Wed, 23 Apr 2025 11:25:05 -0400</pubDate><a10:updated>2025-08-04T11:11:41-04:00</a10:updated><link>/Support/Forum/spirateam/issues-questions/3030.aspx</link></item><item><guid isPermaLink="false">messageId=7199</guid><author>Victoria D (nino.diasamidze@inflectra.com)</author><title> Hello Zoltan,  I think it would be better to use a Component - you can simply create a set of custo</title><description> 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 - </description><pubDate>Wed, 23 Apr 2025 11:45:20 -0400</pubDate><a10:updated>2025-04-23T11:45:20-04:00</a10:updated><link>/Support/Forum/spirateam/issues-questions/3030.aspx#reply7199</link></item><item><guid isPermaLink="false">messageId=7202</guid><author>Zoltan Borbas (zoltan.borbas@harptechnologies.com)</author><title> OK. Thanks. I will take a look. </title><description> OK. Thanks. I will take a look. </description><pubDate>Thu, 24 Apr 2025 08:17:42 -0400</pubDate><a10:updated>2025-04-24T08:17:42-04:00</a10:updated><link>/Support/Forum/spirateam/issues-questions/3030.aspx#reply7202</link></item><item><guid isPermaLink="false">messageId=7290</guid><author>lyly brown (lyly.gm19@gmail.com)</author><title> Thank you so much, Zoltan, for the helpful advice and clear instructions. I will consider creating </title><description> Thank you so much, Zoltan, for the helpful advice and clear instructions. I will consider creating the Component as you suggested! </description><pubDate>Thu, 12 Jun 2025 11:03:02 -0400</pubDate><a10:updated>2025-06-13T08:00:26-04:00</a10:updated><link>/Support/Forum/spirateam/issues-questions/3030.aspx#reply7290</link></item><item><guid isPermaLink="false">messageId=7293</guid><author>Terrill Balistreri (janage8220@regerina.com)</author><title> You can set environment variables like `TEST_BED=TB01` as part of the execution context. Make sure </title><description> 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. </description><pubDate>Wed, 18 Jun 2025 07:38:33 -0400</pubDate><a10:updated>2025-06-18T10:34:19-04:00</a10:updated><link>/Support/Forum/spirateam/issues-questions/3030.aspx#reply7293</link></item></channel></rss>