...

However, by default, no notifications will configured for those events upon installation; you'll need to add, and therefore enable, them explicitly.

Global settings

There are two global settings related with Test Run notifications:

• XXX: for defining who can use the "Add/Disable Test Run notifications" option in the project settings, since it can affect the related Notification Scheme
• YYY: for defining the final statuses for which the "Test Run Status set to Final" and "Precedent Test Run Status set to Final"

For more information on these settings, please see Global Preferences.

Project Setup

Detailed setup

...

There is a quick setup, that will create a notification for each Test Run related event and will configure it for the "current assignee".

This option will only be available for 

1. go to project settings => Summary
2. from the Actions menu, choose "Enable Test Run notifications". Note that this will impact the Notification Scheme being used by this project and all other projects that also use it.
   
3. For each Test Run related event, a notification will be created and assigned to the "current assignee"; please have a look at the Events section below, for clarification on the meaning.
   

Events

Test Run Assigned

The aim of this event is to notify a user (or users) that a Test Run has been assigned, so the tester can proceed with testing.

This event is triggered whenever a Test Run is assigned to some user.

...

Test Run Status set to Final

The aim of this event is to notify users that a Test Run has been complete/finished (i.e. its current status is a final one).

This event is triggered whenever a Test Run is changed to a final status. For more information on final statuses, see Manage Test Statuses.

...

Precedent Test Run Status set to Final

The aim of this event is to notify a user (or users) whenever a different user has finished running the previous Test, in the context of some Test Execution involving multiple testers.

This event is triggered whenever the previous Test Run (i.e. the one immediately before, accordingly to the ranking within the Test Execution) is changed to a final status and the Test Run assignee of the previous run is different from the Test Run assignee that follows it. For more information on final statuses, see Manage Test Statuses.The aim of this 

The event is triggered for the related Test Execution issue. This means that, in the notification configuration screen, most of the fields (e.g. "Reporter", "Project Lead", "Component Lead", "Project Role", "All Watchers", "User/Group custom field value") refer to the associated Test Execution issue or to the Test Execution issue's project. 

...