The elements explorer and element code generation depend on the exact order of tests - alphabetical and folder. For example if a project contains test A then B and both include steps and their elements with pages which should merge, project load will generate Page A (from test A) then loading test B and finding the same page compare logic will merge those elements to Page A.

This algorithm works in general except in cases of coded step and element generation for tests which are renamed or moved between folders. Since the project load can generate Page B in the case above and then merge Page A elements to B, this can result in compile errors on run with the need to manually fix the coded element reference.

Test Studio needs a more reliable mechanism of element code generation so that it doesn't depend on the exact test order upon project load.