Allow users to have a custom case field called 'aliases' which describe the past/future names of a test. Do the translation for reporting and spawning; and cache a mapping locally which is refreshed any time we get a cache miss. Also update testrail-results to get metrics correctly.
Be sure to update POD with RATIONALE:
To preserve history across test renames, it is necessary to keep track of what a test has been renamed as. This would be easy using a git based test management system, but such a thing does not exist. When considering testrail as the canonical source of 'what do i run' this gets complicated when you have multiple branches and LTS tiers having test runs going on actively.
Allow users to have a custom case field called 'aliases' which describe the past/future names of a test. Do the translation for reporting and spawning; and cache a mapping locally which is refreshed any time we get a cache miss. Also update testrail-results to get metrics correctly.
Be sure to update POD with RATIONALE:
To preserve history across test renames, it is necessary to keep track of what a test has been renamed as. This would be easy using a git based test management system, but such a thing does not exist. When considering testrail as the canonical source of 'what do i run' this gets complicated when you have multiple branches and LTS tiers having test runs going on actively.