About

Hooks are special script functions that run before or after you execute a BDD script or a feature file. If you have a programming background, you can consider them as event handlers.

TestComplete supports the following hooks:

Hook	Description
`BeforeFeature`	The test engine calls this hook before executing of a feature file (that is, before you run all the scenarios defined in this file).
`AfterFeature`	This hook works after execution of a feature file.
`BeforeScenario`	The test engine calls this hook before execution of a BDD scenario. If you run a feature file that contains multiple scenarios, the test engine will call this hook for every scenario.
`AfterScenario`	The test engine calls this hook after execution of a BDD scenario. If you run multiple scenarios, the test engine will call this hook for every scenario.

Syntax

You can define hooks in any script unit that belongs to the same project as your BDD scenario or feature file. Here are the examples of simple hook syntax:

JavaScript

BeforeFeature(function (feature){
  // Perform some action before running a feature file, for example:
  Log.Message("Before running the " + feature.Name + "feature file");
})

AfterFeature(function (feature){
// Perform some action after executing a feature file, for example:
  Log.Message("The " + feature.Name + " feature file has been executed");
})


BeforeScenario(function (scenario){
  // Perform some action before running a scenario, for example:
  Log.Message("Before running the " + scenario.Name + "scenario");
})

AfterScenario(function (scenario){
  // Perform some action after executing a scenario, for example:
  Log.Message("The " + scenario.Name + " scenario has been executed");
})

Python

@beforefeature
def someFunc(feature):
  # Perform some action before running a feature file, for example:
  Log.Message("Before running the " + feature.Name + "feature file")


@afterfeature
def someFunc(feature):
  # Perform some action after executing a feature file, for example:
  Log.Message("The " + feature.Name + " feature file has been executed")


@beforescenario
def someFunc(scenario):
  # Perform some action before running a scenario, for example:
  Log.Message("Before running the " + scenario.Name + "scenario")


@afterscenario
def someFunc(scenario):
  # Perform some action after executing a scenario, for example:
  Log.Message("The " + scenario.Name + " scenario has been executed")

VBScript

' [BeforeFeature]
Sub SomeFunc(feature)
  ' Perform some action before running a feature file, for example:
  Log.Message("Before running the " + feature.Name + "feature file")
End Sub

' [AfterFeature]
Sub SomeFunc(feature)
  ' Perform some action after executing a feature file, for example:
  Log.Message("The " + feature.Name + " feature file has been executed")
End Sub

' [BeforeScenario]
Sub SomeFunc(scenario)
  ' Perform some action before running a scenario, for example:
  Log.Message("Before running the " + scenario.Name + "scenario")
End Sub

' [AfterScenario]
Sub SomeFunc(scenario)
  ' Perform some action after executing a scenario, for example:
  Log.Message("The " + scenario.Name + " scenario has been executed")
End Sub

DelphiScript

// DelphiScript does not support BDD.

C++Script, C#Script

BeforeFeature(function (feature){
  // Perform some action before running a feature file, for example:
  Log["Message"]("Before running the " + feature["Name"] + "feature file");
})

AfterFeature(function (feature){
// Perform some action after executing a feature file, for example:
  Log["Message"]("The " + feature["Name"] + " feature file has been executed");
})


BeforeScenario(function (scenario){
  // Perform some action before running a scenario, for example:
  Log["Message"]("Before running the " + scenario["Name"] + "scenario");
})

AfterScenario(function (scenario){
  // Perform some action after executing a scenario, for example:
  Log["Message"]("The " + scenario["Name"] + " scenario has been executed");
})

As you can see, all the hook functions use only one parameter. It is either the Scenario or Feature scripting object that corresponds to the scenario or feature being run, and the test engine passes this parameter to the hook. You can use it to check the name of the scenario or feature you run, and then perform or skip certain actions for some scenarios or features. See below for examples.

What actions to perform in hooks

Before... hooks

In Before... hooks, you can perform some initialization actions, for example:

In BeforeScenario, you can post an image of your application’s window to the test log to be aware of the application state before running a scenario.

Example

ExampleExample
The following code snippet posts an image of the entire screen (desktop) to the test log before the test engine starts running a BDD scenario.

JavaScript, JScript

Python

VBScript

DelphiScript

C++Script, C#Script
Copy Code

JavaScript, JScript

BeforeScenario(function (scenario){
  Log.Picture(Sys.Desktop.Picture(), "Before starting '" + scenario.Name + "'");
})

Python

@beforescenario
def someFunc(scenario):
  Log.Picture(Sys.Desktop.Picture(), "Before starting '" + scenario.Name + "'")

VBScript

' [BeforeScenario]
Sub foo(scenario)
  Log.Picture Sys.Desktop.Picture(), "Before starting '" + scenario.Name + "'"
End Sub

DelphiScript

  // DelphiScript does not support BDD.

C++Script, C#Script

BeforeScenario(function (scenario){
  Log["Picture"](Sys["Desktop"]["Picture"](), "Before starting '" + scenario["Name"] + "'");
})
In BeforeFeature, you can read a data file that is used by multiple scenarios in your feature file.

Example

ExampleExample

JavaScript, JScript

Python

VBScript

DelphiScript

C++Script, C#Script
Copy Code

JavaScript, JScript

var fileData; // Global variable

BeforeFeature(function (param1) {
  // Read file data
  fileData = aqFile.ReadWholeTextFile("c:\\data\\test-data.txt", aqFile.ctUTF8);
})

Python

fileData = "" # Global variable

@beforefeature
def someFunc(param1):
  # Read file data
  fileData = aqFile.ReadWholeTextFile("c:\\data\\test-data.txt", aqFile.ctUTF8)

VBScript

Dim FileData ' Global variable

'[BeforeFeature]
Sub foo(param1)
  ' Read file data
  FileData = aqFile.ReadWholeTextFile("c:\data\test-data.txt", aqFile.ctUTF8)
End Sub

DelphiScript

  // DelphiScript does not support BDD.

C++Script, C#Script

var fileData; // Global variable

BeforeFeature(function(param1) {
  // Read file data
  fileData = aqFile["ReadWholeTextFile"]("c:\\data\\test-data.txt", aqFile["ctUTF8"]);
})
In BeforeFeature, you can set up a database connection used by scenarios in your feature file.

Example

ExampleExample
The following code snippet connects to the sample database that is part of the additional sample package. You can download this package from support.smartbear.com/downloads/testcomplete/samples/. In your tests, you will need to replace the connection string with the string that matches your database.

To store the Connection object, we use a global variable. This way you can use the Connection object from script functions that are linked to individual test steps. Don’t forget to close the connection at the end of the test run.

For more information on working with databases from test scripts, see Working With Databases.

JavaScript, JScript

Python

VBScript

DelphiScript

C++Script, C#Script
Copy Code

JavaScript, JScript

var dbConnection; // Global variable to store the Connection object

BeforeFeature(function (param1){
  dbConnection = ADO.CreateADOConnection();
  // Specify the connection string
  dbConnection.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;"+
   "Data Source=C:\\Users\\Public\\Documents\\TestComplete 14 Samples\\Desktop\\Checkpoints\\XML\\DataGridViewSample\\OrdersDB.mdb";
  // Suppress the login dialog box
  dbConnection.LoginPrompt = false;
  dbConnection.Open();
})

Python

dbConnection = "" # Global variable to store the Connection object

@beforefeature
def someFunc(param1):
  global dbConnection
  # Create a Connection object
  dbConnection = ADO.CreateADOConnection()
  # Specify the connection string
  dbConnection.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;" + \
  "Data Source=C:\\Users\\Public\\Documents\\TestComplete 14 Samples\\Desktop\\Checkpoints\\XML\\DataGridViewSample\\OrdersDB.mdb";
  # Suppress the login dialog box
  dbConnection.LoginPrompt = False
  dbConnection.Open()

VBScript

Dim dbConnection ' Global variable to store the Connection object

' [BeforeFeature]
Sub foo1(param1)
  Set dbConnection = ADO.CreateADOConnection()
  dbConnection.ConnectionString = _
    "Provider=Microsoft.Jet.OLEDB.4.0;"+ _
    "Data Source=C:\Users\Public\Documents\TestComplete 14 Samples\Desktop\Checkpoints\XML\DataGridViewSample\OrdersDB.mdb"
  ' Suppress the login dialog box
  dbConnection.LoginPrompt = False
  dbConnection.Open
End Sub

DelphiScript

  // DelphiScript does not support BDD.

C++Script, C#Script

var dbConnection; // Global variable to store the Connection object

BeforeFeature(function (param1){
  dbConnection = ADO["CreateADOConnection"]();
  // Specify the connection string
  dbConnection["ConnectionString"] = "Provider=Microsoft.Jet.OLEDB.4.0;"+
   "Data Source=C:\\Users\\Public\\Documents\\TestComplete 14 Samples\\Desktop\\Checkpoints\\XML\\DataGridViewSample\\OrdersDB.mdb";
  // Suppress the login dialog box
  dbConnection["LoginPrompt"] = false;
  dbConnection["Open"]();
})

After... hooks

In After... hooks, you can perform some finalization actions, for example:

In AfterScenario, you can post an image of the tested application’s window to the test log to get information on the application status at the end of the scenario run.

Example

ExampleExample
The following code snippet posts an image of a tested application to the test log after the test engine completes a BDD scenario.

As a tested application, we use the Orders sample desktop application that comes along with TestComplete. In your code, you will need to replace the lines that get the Process and Window objects with the code that corresponds to your tested application.

JavaScript, JScript

Python

VBScript

DelphiScript

C++Script, C#Script
Copy Code

JavaScript, JScript

AfterScenario(function (scenario){
  var p = Sys.Process("Orders"); // Get process
  var w = p.WinFormsObject("MainForm"); // Get window
  Log.Picture(w.Picture(), "The '" + scenario.Name + "' scenario is over");
})

Python

@afterscenario
def someFunc(scenario):
  p = Sys.Process("Orders") # Get process
  w = p.WinFormsObject("MainForm") # Get window
  Log.Picture(w.Picture(), "The '" + scenario.Name + "' scenario is over")

VBScript

' [AfterScenario]
Sub foo(scenario)
  Set p = Sys.Process("Orders") ' Get process
  Set w = p.WinFormsObject("MainForm") ' Get window
  Log.Picture w.Picture(), "The '" + scenario.Name + "' scenario is over"
End Sub

DelphiScript

  // DelphiScript does not support BDD.

C++Script, C#Script

AfterScenario(function (scenario){
  var p = Sys["Process"]("Orders"); // Get process
  var w = p["WinFormsObject"]("MainForm"); // Get window
  Log["Picture"](w["Picture"](), "The '" + scenario["Name"] + "' scenario is over");
})
In AfterFeature (or even in AfterScenario), you can send a notification to your teammates about completion of the run.

Example

ExampleExample
To send an email, we will use th BuiltIn.SendMail(...) function. See also Sending Email From Scripts.

JavaScript, JScript

Python

VBScript

DelphiScript

C++Script, C#Script
Copy Code

JavaScript, JScript

AfterFeature(function (feature) {
  SendMail("[email protected]",
           "mail.mycompany.com",
           "John Smith",
           "[email protected]",
           feature + ": The test is over",
           "");
})

Python

@afterfeature
def someFunc2(feature):
  SendMail("[email protected]", "mail.mycompany.com", "John Smith", "[email protected]", feature + ": The test is over", "")

VBScript

Sub foo(feature)
  Call SendMail("[email protected]",
                "mail.mycompany.com",
                "John Smith",
                "[email protected]",
                feature + ": The test is over",
                "")
End Sub

DelphiScript

  // DelphiScript does not support BDD.

C++Script, C#Script

AfterFeature(function (feature) {
  SendMail("[email protected]",
           "mail.mycompany.com",
           "John Smith",
           "[email protected]",
           feature + ": The test is over",
           "");
})
In AfterFeature, you can close a database connection that your scenarios used.

Example

ExampleExample
The code snippet below assumes that the global dbConnection variable stores the Connection object created in the BeforeFeature hook function.

JavaScript, JScript

Python

VBScript

DelphiScript

C++Script, C#Script
Copy Code

JavaScript, JScript

var dbConnection; // Global variable that stores the Connection object

AfterScenario(function (param1){
  dbConnection.Close();
})

Python

dbConnection = "" # Global variable that stores the Connection object

@afterscenario
def someFunc(param1):
  global dbConnection
  dbConnection.Close()

VBScript

Dim dbConnection ' Global variable that stores the Connection object

' [AfterFeature]
Sub foo(param1)
  dbConnection.Close
End Sub

DelphiScript

  // DelphiScript does not support BDD.

C++Script, C#Script

var dbConnection; // Global variable that stores the Connection object

AfterScenario(function (param1){
  dbConnection["Close"]();
})

Tip

If you open a connection or file, or allocate other resources at the beginning of the run, close this connection or file, or release the resources at the end of the run.

In TestComplete versions prior to version 14.90, if a test run was terminated on an error, TestComplete could not reach the After… hooks. As a workaround, we recommended creating an OnLogError event handler and using it to perform required actions. Starting from version 14.90, TestComplete handles the hooks correctly and runs the After… hooks even if the test run is stopped upon an error. If you have tests created in a TestComplete version prior to 14.90 and you use the described workaround, you may face compatibility issues. We recommend that you update your tests to use the After… hook to close opened connections or files and release allocated resources.

Tagged hooks

You can assign tags to feature files and scenarios, and run scenarios and files by tags. You can also make hooks work only for those feature files and scenarios that have specific tags assigned, that is, you can implement tagged hooks. To do this, check the scenario’s or feature file’s tags at the beginning of the hook function and run the hook body depending on the result of the check. The sample hook code below demonstrates how you can implement this. The sample hooks work only for those scenarios that have the @tagA tag assigned, and don’t have @tagB assigned:

JavaScript, JScript

BeforeScenario(function (scenario){
  // param1 contains the Scenario object
  if (scenario.Tags.Contains("@tagA") &&
      !scenario.Tags.Contains("@tagB")) {
   // Run the hook code
   // ...
  }
})

Python

@beforescenario
def someFunc(scenario):
  if scenario.Tags.Contains("@tagA") and not scenario.Tags.Contains("@tagB"):
    # Run the hook code
    # ...

VBScript

' [BeforeScenario]
Sub SomeFunc(scenario)
  ' param1 contains the Scenario object
  If scenario.Tags.Contains("@tagA") And _
     Not scenario.Tags.Contains("@tagB") Then
   ' Run the hook code
   ' ...
  End If
End Sub

DelphiScript

// DelphiScript does not support BDD.

C++Script, C#Script

BeforeScenario(function (scenario){
  // scenario contains the Scenario object
  if (scenario["Tags"]["Contains"]("@tagA") &&
      !scenario["Tags"]["Contains"]("@tagB")) {
   // Run the hook code
   // ...
  }
})

To adopt this example to another hook, simply replace BeforeScenario with the desired hook name. For information on working with tags, see Tags.

More notes

The actions you perform in hooks functions are not reflected in feature files and scenarios and are hidden for their authors (in some organizations, BDD scenarios are written by subject matter experts or product managers, while test steps are automated by the QA team or automation engineers). This might be important if the test authors should know about the initialization actions the BeforeScenario or BeforeFeature hooks perform. To make these actions more visible to the authors, you can suggest that they use the Background keyword in BDD tests.
You can define multiple hook functions of the same time, for example, multiple scripts functions as a BeforeScenario hook. TestComplete will execute them all. However, their execution order is not configurable.
TestComplete ignores the result value of hook functions.

Using Hooks

About

Syntax

What actions to perform in hooks

Before... hooks

After... hooks

Tip

Tagged hooks

More notes