When you modify custom step types, consider the following caveats so you can avoid making changes that might jeopardize compatibility.

  • Ensure that previously configured steps behave properly when you execute the steps using the modified custom step type.
  • Ensure that new step instances based on the modified step type behave properly when you save a sequence file to an earlier version of TestStand that uses the original custom step type.
  • Do not rename custom step type properties or change the functionality of existing properties. For example, when you have an existing property that performs a specified task and you later decide you want the property to do something completely different in a future instance of the step type, you break compatibility.
  • When you create new properties, provide default values that preserve the functionality of previously created steps.
  • When you extend enumerated values, do not change the functionality of previously used values.