...

Since the Test Run is not an issue type, events are triggered for the related Test Execution; this means that the notification destination fields recipients fields are mostly related with the Test Execution. However, in some events there can be some difference on the semantics of the fields (e.g. "current assignee" may be the assignee of the Test Run instead of the Test Execution issue).

...

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 some 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.

Image Added

Project Setup

Quick setup

Enable notifications

...

...

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.
   Image RemovedImage Added
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 of this specific destinationrecipient.
   

Disable notifications

There is a quick way to "disable" (i.e. remove) notifications for each Test Run related event.

...

...

1. go to project settings => Summary
2. from the Actions menu, choose "Disable Test Run notifications". Note that this will impact the Notification Scheme being used by this project and all other projects that also use it.
   

...

1. Image Added

Detailed setup

In order to enable notifications in some project, you need to:

...

• Whenever a specific Test Run is individualy individually assigned to some user (e.g. in the Test Execution screen), the "Test Run Assigned" event is triggered;
• Whenever a Test Execution is created, all Test Runs are assigned by default to the Test Execution assignee. In this case, the "Test Run Assigned" event is not triggered (possibly, the user will be already notified because of issue created event);

• Whenever several Test Runs are assigned to some user using the bulk operation, in the Test Execution screen, the user is asked if email should be sent (i.e. if the event should be triggered).
  
  
  

  Info
  title Please note
  The "Send mail" option is only available if there is a notification assigned to the "Test Runs Assigned" event.

...