Issue with ATF Test Export

[kkrushkov]

Hello, guys!

I’m currently experiencing an issue with ATF tests. I want to export an ATF test from one instance to another. The test covers a service catalog item and includes the following test steps:

1. Open a Catalog Item
2. Variable State Validation
3. Set Variable Values

In steps 2 and 3, I need to specify a catalog item, but there’s no option to select it from previous steps. When I import the test into the second instance, the catalog item field is empty, causing the test to fail. The goal of this export is to allow the user to run the test in the second instance without needing to manually specify the catalog item. 

Is there a way to address this issue, or is it a current limitation of ATF functionality?

[Josh Pirozzi]

Hi @kkrushkov,

If you're building the ATF Test, you should be able to capture the Test and Test Steps in an Update Set, and then migrate that between Instances. 

When creating a Test for a Catalog Item, we go with the following steps:

1. Open a Catalog Item (SP) - This is where you'll specify the Catalog Item & Portal View you'd like the Test to validate on.
2. Variable State Validation (SP) - This is where you can confirm Visibility / Mandatory based on Variable Selections/Completions.
3. Set Variable Values (SP) - This is where you'll set all variables after selecting the Item you'd like to validate.

The Test Should automatically select the Catalog Item in each Step after 1, but in the case it doesn't you can always just add it in to the 'Catalog Item' Reference Field on each Test Step.

Thanks & I hope this helps!

-Josh

[kkrushkov]

Hi, @Josh Pirozzi 

The problem I’m facing occurs when I export the ATF test via an update set to the second instance. In this new instance, the reference to the catalog item in the test steps is lost, likely due to instance differences. The goal of this export is to allow the user to run the test in the second instance without needing to manually add the catalog item to each test step.

[Josh Pirozzi]

Hi @kkrushkov,

It should retain the step if the Catalog Item sysID is the same in every Instance.

When you build a Catalog Item, are you building it in each Instance individually? Or, are you building it in one Instance and then moving it to the other Instances via an Update Set?

Thanks,

Josh

[kkrushkov]

Hi, @Josh Pirozzi 

Thank you for your engagement on this topic.

I am creating the fields individually within each instance, aware that the differing sys IDs might be contributing to the issue. However, I’ve tested other fields—also created separately with unique sys IDs—and they function correctly. For example, a record in the cmn_location table continues to work as expected. This suggests that the sys ID differences might not be the primary issue, though it appears to be impacting certain fields.

Could you provide insight into why some fields work despite sys ID differences, while others do not?