Code-Behind File

Standalone version

Once you have created a coded step, click the View Entire Code Behind File button to see the entire code-behind file View code behind button.

View code behind

  • Just like a step that has been converted to code, a method in the code-behind file is represented as a step in the Steps tab.

  • Do not remove the CodedStep attribute. This is how Test Studio recognizes custom coded steps versus other methods it should ignore.

  • The name of the method becomes the step name. The Coded Step attribute description is listed as the description in the Steps tab.

  • The code-behind file has access to all Telerik run-time objects, like ActiveBrowser. This is an identical coding experience to the Telerik Testing Framework.

Visual Studio plugin

Add Code Behind File

A code-behind file is automatically generated the first time you select Edit in Code from the Test Step Context Menu (performed on step 4 above). The code-behind file is nested under the parent test in Solution Explorer:

Code Behind File