Using the setting ‘Use separate ScreenCaptures folder’ in FTR-a/Citratest is not working--we don' (94517)

Using the setting ‘Use separate ScreenCaptures folder’ in FTR-a/Citratest is not working--we don't get screen captures on script fail on our failedimagePath like we want

When preparing the ini file native scriptname.ini (when FTR modifies the Citratest native script.ini) to be packaged for FTR and prepared to move to a new folder tree, paths are modified to new values--relative values using the "." at the beginning of the path. FTR does change the imagePath and searchPath, but the failedImagePath is a new feature in CitraTest so it wasn’t handled in the existing code. FTR should not be changing the failedImagePath but it is. It is getting that "dot" prepended.

The failedImagePath is set on the Citratest UI menu 'Scripting' | 'Scripting Options' dialog under "Set script failure screen capture folder". But this path is only used if you select "Use separate screen captures folder" in Playback Options. Else, the screen captures just go into the main imageDir.

If failedImagePath is configured to be a relative path and "Use Separate Screen Caps Folder" is selected, the Capture Screen on script fail does not work because the screen capture path becomes imagePath + "." + failedimagePath instead of just imagePath + failedImagePath. The "." in front makes the path invalid. The path would need to be a relative path that looks like this: "ScreenCapsFolder\" with no "dot" so it can be seamlessly appended to the imagePath. (e.g. "C:\Myscripts\MyImages\" + "ScreenCapsFolder\" would work).

This problem doesn’t really have anything to do with the failedImagePath directly. It is really with the ImagePath. The failedImagePath also contains the imagePath directory as its base (by default). When FTR is preparing the native Citratest script.ini file for FTR, updating the imagePath to prepare to move to a new folder tree, it attempts to replace the existing path with a new string. Instead of only replacing that one place it changes any instance of that path in the entire .ini file. Since the failedImagePath shares (by default) the same base as the imagePath, it gets replaced also. This is being tracked as def

WORKAROUND

Do not use the "Use Separate Screen Caps Folder" option. If you explicitly change the failedImagePath to a absolute path that does not contain the imagePath directory name (maybe just "C:\FailScreens\" ) it _may_ work.

STATUS

Waiting for fix in a future release of FTR.

Since the failedImagePath is a fairly new addition to the script.ini file (last 6 months or so) FTR has never intended to change it, it didn’t exist.