My team uses Analyzer Rules to enforce best practices for developers across sequence files and workspaces with great results. However we would love to be able to also provide rule checking and warnings for developers on some basic *.tsd file content such as Installer Name field, and build-path & installation-path/image-path, etc... New (or rusty!) developers often miss steps in their configuration and needlessly struggle with badly behaving deployments.
As TSD files do not appear to have an API available from TestStand at this time nor conform to a json/xml syntax internally, for easy parsing via 3rd party tools, some method(s) for 'reading' file (or converting to readable syntax) may also be required in order to build rules effectively?
