conversion problem Teststand 2014 to 2019

[Tonnie]

Hello 

When I convert a sequence file from Testand 2014 to Teststand 2019 i see differences in the Goto steps.

As you can see in the picture below the step should jump to "wait front door open" but when i open the teststep the destinaiton is "wait check door closed"

Is this a know issue or do i do something wrong

Tonnie_0-1788337424276.png

[Oli_Wachno]

---

@Tonnie wrote:
[...]

 do i do something wrong

[...]

---

// Irony on
Yes... you are using GOTOs and you are updating from an ancient version to a sligthly less ancient version

// Irony off

This behaviour sounds strange... what you could investigate though: save the File in 2014 in XML and save the imported version in 2019 as well in XML (Edit --> Sequence File Properties)

Use TestStand Diff/ Merge Tool to compare and especially take a look at these Goto Steps

Spoiler

Nigels Answer to this:

Yes. A **GOTO** should target a **Label** step, and that target should survive step reordering. So if an upgrade appears to retarget a GOTO, that usually points to one of these issues:

| Likely cause | What to check |
|---|---|
| **Broken label reference** | Open the GOTO step and inspect **Destination**. Does it still point to the intended **Label**? |
| **Duplicate or renamed labels** | Check whether migration created multiple labels with similar names or changed descriptions. |
| **Reference-by-index behavior from older content** | Older sequences sometimes behave as if the target was tied to step position after edits/imports/copy-paste. |
| **Cross-step-group logic** | Verify the target is in a valid location. GOTO behavior across **Setup / Main / Cleanup** can be tricky. |
| **Sequence merge/type conflict side effects** | If the file was mass-converted, some internal references may have been rewritten unexpectedly. |

### Best path
1. Compare the **TS 2014** and **TS 2019** versions side by side.
2. For one bad GOTO, note:
- source step name
- expected label
- actual label after upgrade
- whether steps were inserted/deleted before conversion
3. Prefer **unique Label steps** as targets, not ordinary steps.

### Common mistake to avoid
Do **not** trust the label *description* alone; verify the actual selected destination in the GOTO configuration.

If you want, I can help you build a **systematic check list** for migrated sequences, or troubleshoot **one specific sequence** if you share the step layout.

* AI generated information

Hope this helps

[Tonnie]

Thanks for you response

I think i solved the problem. The sequence file was first converted from TS2014 to TS2019 and then parts of the sequence where copied to a new sequence file. Then the goto probably lost its reference

so a copy of teststeps that include a Goto will not work. could that be the case ?

[Oli_Wachno · Accepted solution]

The part with copying would have been a good hint 😉

---

@Tonnie wrote:
[...]

so a copy of teststeps that include a Goto will not work. could that be the case ?

---

Guess this depends on how you define the references. Anyway, I would be careful when copying.