BDD Framework: How to avoid to lose information

All the information set using the inspector are stored in particular arrays. Usually, the framework hides them, but you can consider them as public properties of components attached to the integration test object, so they follow the same rules as the standard component properties:

  • Parameters: The values of the parameters for the Dynamic Components Methods are stored in the ParametersValuesStorage fields. If you delete, rename or change their types, you are going to lose all the data stored inside because the inspector could lose the pointer to them. Furthermore, if you delete, rename or change the type of a parameter inside a method signature, the framework loses the pointer to the parameter and the value stored for it.

  • Dynamic Step Methods: The values you can read on the combo boxes for the Dynamic Tests are stored as strings inside the BDD Extension Runner component. If you rename a method or a class, the runner loses the pointer to the methods. When it happens, the runner shows an error, asking you to fix it.

  • Do not remove the Dynamic Components from the integration test: if you do that, all the related data will be deleted by the inspector.

  • Do not reset your components or the BDD Extension Runner component: if you do that, all the related data will be deleted by the inspector.

 

Q: What can I do if I notice I lose data from the Inspector?

If the action that made you lose the data was made on the Inspector, just use the Undo feature.

If you have deleted or renamed something inside your BDD Component, the Framework usually tries to protect the data stored inside the BDD Extension Runner giving you an error and letting you fix it. Unfortunately, if the data lost were stored inside the component (the values of the parameters) you could have lost them forever.

 

 

Back to: BDD Framework: How to create your own static test Read next: BDD Framework: Error and problems handling

 

© 2017 Hud Dimension. All Rights Reserved.

Search