Fixing a Save Test Case Variable Step After an App Change - Best Practice
When your app changes, a Save Test Case Variable step may read from the wrong element. Pick the fix that matches your situation.
- The element moved or the UI changed, and you want to keep one variable
- Use Update Baseline. The variable keeps its name and reads from the new element. The update applies to every test that uses the template.
- You already recorded a new variable and want old steps to use it
- Use Override Variable. Old steps pick up the new value. Two variables remain.
Best practices
- Use unique variable names so it's always clear which variable a step uses.
- Don't disable a Save Test Case Variable step to change what it captures. Execution falls back to the recorded value. Use Update Baseline instead.
