Coded steps in Progress® Test Studio® for APIs can be used to execute C# or Visual Basic code as part of the test execution. Each coded step points to and executes a method in its test case's code-behind file. Use a coded step for a scenario that requires more complexity than what can be achieved with the functionality of the rest of the provided step types.
A coded step can be added to a test case using the Add Step menu in the test's context menu in the project explorer
or using the Add a Step button in the test explorer.
If this is the first time you are adding a coded step to this project, you will be prompted to select a coding language for the project (C# or Visual Basic).
Adding a coded step to a test case will create a code-behind file, associated to that test. You can also choose to manually create the code-behind file before creating any steps. To do that, use the "Add Code-Behind" option in the test's context menu in the project explorer.
Next to each test case that has a code-behind file, you will sea a button in the project explorer, that can be used to open the code-behind file.
Once created, the test's code-behind file cannot be deleted from the UI. If you wish to remove it, you should create a new test case, move your non-coded steps there and delete the old test case (which will delete its code-behind file too).
When a new coded step is created, you need to select the method that should be executed when the step is run. You can choose between any already existing public method in the test's code-behind file or click on
<New Test Method> which will create a new method for you.
Note that if you later rename the method in the code-behind file, that will break the coded step mapping. Once a method name is changed, you need to open any coded step that used to point to it and remap it to the new method name or another existing method. A warning indicator in the project explorer will guide you whenever there is a broken or missing coded-step-to-method reference as shown in the following images.
Coded steps can have a condition. Use it whenever you wish to skip the step's execution based on a chosen criteria.