The second step of the installation is to configure the controller so it will be able to communicate with ALM in order to retrieve the tests from ALM and publish the results of the test runs back into ALM.
First, you will need to register the ALM DLLs used for accessing the ALM API. You will need admin right on the Controller.
Open Internet explorer as an administrator and go to ALM, then click on tool:
Then go to HP ALM Client Registration:
Finally, click on Register HP ALM to trigger the registration:
The following message should appears at the end of the installation:
Below configuration entries are mandatory and needs to be set to the file …\step-controller-X.Y.Z\conf\step.properties.
Other configuration entries are documented directly in the step.properties file.
Connect on your project and go to the “Test Plan” tab. A new “stepRunnerTP” button should be available
Create the following demo test, using basic logic blocks that can be used with step for ALM:
Select it and click on the new “stepRunnerTP” button. A new Internet Explorer with your step Controller should popup:
Log into the controller, you should get the following error. This is normal as the step Controller has yet to know how to communicate to the ALM instance:
You can then do the same validation on the “Test Lab” tab. The button will be called stepRunnerTL:
You can try to execute again from the test lab (so that we can also check the reporting of the execution back to ALM) the small demo test created before:
Contrary to previously, the controller is now able to query ALM about test information and you should be able to start the execution from the controller GUI:
You should then be able to see in step the result of the execution: (Note that we still have a technical error due to the fact that we execute a non-existing Groovy macro; this point will be addressed in the next section).
If you go back to ALM, you should now see the summary of this execution in the “Execution Grid” of the “Test Lab” (a refresh of the view may be needed):
And also the execution details in the “Test Runs”: