Custom Fields

The ActiveControl / Jenkins integration for automated testing relies on Jenkins 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.

The information stored in these custom field(s) information is passed over to Jenkins as part of the outbound Integration (along with the Business Task and Transport Form information) – and the Customer Jenkins Administrator would then need to pass this information over from Jenkins to the test automation tool to trigger the relevant testing.

Figure: Example of test script information being stored in a Business Task custom field. This data is then passed over to Jenkins, for triggering the corresponding Testing scripts.

* If multiple automated test cycles are required as part of an ActiveControl workflow (eg triggering Smoke Tests as part of a QA system and triggering Regression Tests as part of a Pre-Production system), then the recommendation would be to have multiple Custom Fields. Again, it would be the responsibility of the Customer’s Jenkins and Test Tool to call the relevant scripts and triggering of scripts via Jenkins.

* All custom fields are sent across as part of the XML – ie there is no need to define specific Custom Fields as part of the integration configuration.