Testing within ActiveControl is typically done at a Business Task level. Testers are assigned via the [Testing] subscreen on the Business Task.

Figure: Testing subscreen on the Business Task

The Testing subscreen within a Business Task is split into two sections:

1. Testing History
2. Testing Assignments

Testing History.

Testing History shows a read-only history of Testing that has been completed on a Business Task.

Any attachments (either uploads or URL linled) added during Test Signoff process is seen within the Testing History section of the Business Task, and not in the Attachments tab of the Business Task.

Testing Assignments

Testing Assignments is where Tester(s) can be assigned to individual Business Tasks. It is possible to assign a Tester at different levels:

  • All System Tester – this enables the Tester to sign off any Test Queue
  • Specific Role Tester – this enables the Tester to be assigned to sign off any Targets of a specific Target Role
  • Specific Target Tester – this enables the Tester to be assigned against a specific Target.

It is a mandatory requirement within ActiveControl that at least one user is assigned as a default All System Tester. Depending on your implementation of ActiveControl, the default All System Tester is likely to either be the end-user creating the Business Task, or a batch user if the Business Task is being created automatically via an Integration with another 3rd Party tool such as Jira or ServiceNow.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment