Solved
Changing Properties in a Property Checkpoint
When you wish to edit/modify a Property Checkpoint within a test script, when you double-click on the checkpoint, it brings up the first screen of the checkpoint wizard (which is the object spy window). This window correctly identifies the object that was initially selected, but when you click Next, you get an “Unable to find the specified object” error, or when you select "Select Object in Visualizer" you get an "Unable to select an object in Test Visualizer" error.
You cannot re-select the object from the “Test Visualizer”, as you did initially when creating the checkpoint, and you cannot open the application itself, and then use the object spy from the wizard to reselect the object, as in both cases, you lose focus from the Wizard, so you are stuck not being able to hit next and edit the checkpoint.
You also cannot go into the Workspace>Object Table and edit the object, as it only contains the initial properties there were selected when the checkpoint was created, which defeats the purpose of being able to change/edit the checkpoint to use a different property.
Therefore, is there any way to modify/change a property in a Property Checkpoint, other than to create a new checkpoint from scratch?
You cannot re-select the object from the “Test Visualizer”, as you did initially when creating the checkpoint, and you cannot open the application itself, and then use the object spy from the wizard to reselect the object, as in both cases, you lose focus from the Wizard, so you are stuck not being able to hit next and edit the checkpoint.
You also cannot go into the Workspace>Object Table and edit the object, as it only contains the initial properties there were selected when the checkpoint was created, which defeats the purpose of being able to change/edit the checkpoint to use a different property.
Therefore, is there any way to modify/change a property in a Property Checkpoint, other than to create a new checkpoint from scratch?
- Yes, but the object in question has to be available to TC when you are editing. If you are just trying to edit without the application running and the object visible, TC will be very cranky and pretend it has no idea what you are talking about.
