The ActiveControl / Gitlab integration for automated testing relies on GitLab being able to tell the testing tool what automated tests need to be performed.
In most scenarios, this is best done by the user (ie a Developer or Tester) manually indicating on the the Business Task (or Transport Form) what automated testing scripts should be performed against the particular Change or Transport. This is achieved in the current Integration through the use of custom field(s) on the Business Task or Transport Form (or both depending on the exact Customer requirement); these Custom Fields are configured via the Windows GUI configuration [Fields] tab in the usual way.
Figure: Custom Field creation in the ActiveControl Windows GUI
The information stored in these custom field(s) information is passed over to GitLab as part of the outbound Integration (along with the Business Task and Transport Form information) – and the Customer Gitlab Administrator would then need to pass this information over from GitLab to the 3rd Party test tool to trigger the associated automated testing.
Post your comment on this topic.