How to Reuse a Variable Value Across Two Test Cases

How to Reuse a Variable Value Across Two Test Cases

Overview

Sometimes the same value - for example a batch ID - needs to appear in two different interfaces or test cases, and it must be the exact same value in both. This guide shows how to capture a value from one message and reuse it in another, covering two different setup paths depending on your licensing:

1. Int4 Shield (manual) - without parent/child test case linking. You enter the value once, then re-enter the same value in the second test case.

2. Int4 API Tester (automated) - with parent/child inheritance. The second test case automatically inherits the value from the first, so you never re-enter it manually.

Step-by-step instructions

1. Decide which variable value you want to reuse

▶ Watch at 0:00

Use this approach whenever you need to capture a value from one message and reuse the exact same value in another interface or test case.

1. Identify the field to reuse - typically something like a batch ID in an XML, JSON, or flat file message.

2. Decide which setup path applies to your license:

   • Int4 Shield - manual, no parent/child linking

   • Int4 API Tester - automated, with parent/child inheritance

⚠️ Important: Which path you take depends entirely on licensing. If you do not have an Int4 product license allowing you to link Test Cases , you must use the manual approach described in Step 5.

2. Create a variable in the automation object

▶ Watch at 0:38

Create the variable that will hold the reusable value.

1. Open the relevant Automation Object for the test case.

2. Click Edit.

3. Go to Variables and create a new variable.

4. Give it a clear name and description, for example:

   • Name: batch

   • Description: batch ID

3. Configure the variable to read from the source message and replace the value

▶ Watch at 1:19

Configure the variable action so it both reads the source value and replaces it in the target message.

1. Set the variable action to Read and Replace.

2. Open the edit/configuration view for the variable.

3. In the Read section, choose where the value comes from - for this example, select Read from saved message.

4. Use the expression helper to import the payload from the relevant test case.

5. Select the correct payload type depending on your setup:

   • Payload or

   • Input message for certain test types such as PO Unit Test

6. Use the XPath helper to select the exact field/node you want to capture, such as a custom batch ID field in an IDoc.

7. In the Replace section, choose how the value should be replaced. For the manual path, choose Read user-defined value from test case so the value can be entered at test case level.

4. Save the automation object and enter the variable value at test case level

▶ Watch at 3:02

Save the configuration and provide the actual value that will be used when the test case runs.

1. Save the automation object after configuring the variable.

2. Open the test case details.

3. Look for the new Edit variable values section - this appears only when the variable is configured to read a user-defined value.

4. Enter the desired value for the variable, such as a specific batch ID.

5. Save the variable values.

When the message is sent, the variable uses the value you entered here.

5. Option A - Manual linking with Int4 Shield (no parent/child license)

▶ Watch at 4:05

If you do not have parent/child linking available, repeat the same setup manually for the second interface.

1. Create the same variable in the second Automation Object/test case.

2. Enter the same value again in Edit variable values.

3. Run the test cases one by one, in sequence.

Each test case uses the manually provided value.

⚠️ Note: This is the only option available under an Int4 Shield license. It works reliably but requires you to keep the value in sync by hand across every test case that needs it. If you have an Int4 API Tester license, Step 6 below removes this manual step entirely.

6. Option B - Automated inheritance with Int4 APITester

▶ Watch at 4:49

In Int4 APITester, avoid manually re-entering the same value by having the second test case inherit it automatically.

1. Create the variable again in the second Automation Object, but configure it slightly differently.

2. Keep the action set to Read and Replace.

3. Read the value from the message using the correct XPath for that interface.

4. In the Replace section, choose Read from previous test case instead of a user-defined value.

5. Enter the variable name used in the previous test case, for example batch.

6. Save the automation object.

7. Link the test cases so the second one inherits the variable value

▶ Watch at 6:02

Establish the parent/child relationship so the inheritance configured in Step 6 actually takes effect.

1. Link the second test case to the first as a child of the parent test case.

2. Example shown in the recording: test case 989075 linked to the earlier test case as its parent.

When the test cases run in sequence, the second test case inherits the variable value from the first automatically.

8. Verify that the value was carried forward

▶ Watch at 6:26

Confirm the automated inheritance worked as expected.

1. Run the linked test cases.

2. In the first test case, confirm the variable value was set correctly at the test case level.

3. In the second test case, confirm the value was read from the previous test case.

💡 Tip: Even if the message itself fails to send in a demo environment, you can still verify the variable inheritance directly in the test case details.

Expected outcome

• ✅ A variable is configured on the automation object to Read and Replace a specific field value

• ✅ Option A (Int4 Shield): the same value is entered manually in both test cases and produces consistent results when run in sequence

• ✅ Option B (Int4 APITester): the child test case is linked to its parent and automatically inherits the value, with no manual re-entry

• ✅ The inherited or manually-entered value has been verified in the test case details

Troubleshooting

Related resources

• Int4 Suite Knowledge Center: Variables and Variable Processing