Why do test cases use outdated steps or parameters during campaign execution?

[Mikasa]

Hi everyone,
I am currently dealing with an issue in SquashTM related to test cases and it is starting to affect our daily work quite a bit.
I have a large test repository with more than 600 test cases organized into folders with shared steps and parameters. After some recent updates and restructuring, I noticed that certain test cases do not behave as expected during campaign execution. Some of them seem to use outdated parameter values or older versions of shared steps, even though I already updated and saved everything in the repository.
What confuses me is that when I open those same test cases directly in the library, they display the correct and latest content. However, when I run them inside a campaign, they appear to rely on an older version. I tried duplicating test cases and relinking them, but the issue still happens randomly.
This is becoming a serious concern because it affects the reliability of our regression testing and reporting. I am wondering if there is some kind of versioning or caching behavior that I might not fully understand.
Has anyone encountered this situation before or found a way to fix it?
Geometry Dash

[bennettshaw121]

Have you tried refreshing or re-importing the test cases into the campaign to force it to use the latest version?

[nevisalexander]

It sounds like a frustrating situation with your test cases in SquashTM. The issue you’re experiencing could indeed be related to versioning or caching. Sometimes, test management tools might cache older versions of test cases or parameters, leading to discrepancies during execution. Here are a few suggestions you could try:
Clear Cache: Check if there’s an option to clear the cache in SquashTM, as this might help refresh the data.
Revalidate Links: After updating shared steps or parameters, ensure that all test cases are properly linked to the latest versions.
Check for Dependencies: Sometimes, test cases can have dependencies on other cases or shared steps that may not have been updated correctly.
Reach Out to Support: If the problem persists, consider reaching out to SquashTM support for assistance, as they may have encountered this issue before.