Currently there are caveats when upgrading system definition in VeriStand. It would be helpful to have a tool to help VeriStand developers check and see what type of issue they might run into when upgrading a system definition. Specifically an issue that I've encountered was that my pathing for the upgrade was correct but the mapping of the items turned out wrong. An example of something a tool could help out with is a test for the Model item map. That test would verify that all model maps refer to the fully-qualified path to the item.
JY
Application Engineer, RF and Communications
National Instruments
