Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Go to the Jenkins Server home page.
  2. Click the New Job link or select an existing job.
  3. Enter a Job name (for a new job).
  4. Select Build a free-style software project and click OK.
  5. In the Project Configuration section scroll down to the Build section.
  6. Expand the Add build step drop-down and select Execute functional tests from ALM.
  7. Select one of the ALM servers that you configured in the previous step.
  8. Enter the server credentials, project and domain. For ALM 14, use the API Key client ID and secret as the username and password. Note: If you are using the ALM scheduler, it will run under the Jenkins agent user. For example, if Jenkins is running as a System user, the scheduler will run the tests as a System user. This will not affect test execution. 
  9. Add the test set folders or specific test sets that you want to include, using the ALM path. To add a specific test, add the test name after the test set path.To add multiple entries, click the down arrow on the right of the field and enter each item on a separate line. See the example below.

  10. Optionally, indicate a timeout in seconds after which the job will fail.
  11. Click Advanced to indicate a Run mode (local, remote, or planned host) If you specify a remote host mode, specify a host name. This must be a machine with a valid installation of the testing tool.
  12. Click Apply to save your changes and continue with more build steps. Click Save when you are finished adding build steps.


    Code Block
    Root\testfolder1\testset_a
    Root\testfolder1\testset_b
    Root\testlab_folder
    Root\testlab_folder\testset_a\test-name

...

  1. Go to the Jenkins Server home page.
  2. Click the New Job link or select an existing job.
  3. Enter a Job name (for a new job).
  4. Select Build a free-style software project and click OK.
  5. In the Project Configuration section scroll down to the Build section.
  6. Expand the Add build step drop-down and select Execute tests using ALM Lab Management.
  7. Select one of the ALM servers that you configured in the previous step.
  8. Enter the server credentials, project, and domain. For ALM 14, use the API Key client ID and secret as the username and password. 
  9. If your ALM server version is 12.60 or higher, enter the Client type.
  10. Select a Run Type from the drop down menu (functional test set or build verification suite).
  11. Enter the ID of your run entity (either the test set ID or the build verification suite ID).
  12. Optional: Enter a description of the build step.
  13. Enter a duration (in minutes) for the timeslot. The minimum time is 30 minutes.
  14. Optional: If you have defined an AUT environment configuration in ALM, you can enter the ID here in order to execute your timeslot with specific AUT parameters.
    If you have CDA configured in ALM and want to implement it for this time slot, select the Use CDA for provisioning and deployment checkbox and enter your CDA details.
    Set up the Post Build actions
  15. In the Post-build Actions section, expand the Add post-build action drop-down and select Publish test result.

...

  1. Go to the Jenkins Server home page.
  2. Click the New Job link or select an existing job.
  3. Enter a Job name (for a new job).
  4. Select Build a free-style software project and click OK.
  5. In the Project Configuration section scroll down to the Build section.
  6. Expand the Add build step drop-down and select Execute AUT Environment preparation using ALM Lab Management.
  7. Select one of the ALM servers that you configured in the Configure the connection to your ALM server step.
  8. Enter the server credentials, project name, and domain. For ALM 14, use the API Key client ID and secret as the username and password. 
  9. Enter the ID of the environment for which you want to create/update a configuration.
  10. Select one of the following options to Indicate whether or not to create a new AUT Environment Configuration or update an existing one.
    1. For Create a new configuration named, enter a name for the new configuration.
    2. For Use an existing configuration with ID, enter the ID of your AUT Environment Configuration in ALM.
  11. Optional: Enter a path for a JSON file that contains values for the AUT Environment parameters for the relevant configuration.
  12. Optional: Enter a name of a build environment parameter in order to save the ID of the created/updated configuration for future use.
  13. Add the AUT Environment parameters that you want to update for the created/updated configuration. For each parameter:
    1. Select the type of the parameter from the drop-down menu (Manual, Environment, From JSON).
    2. Enter the full path of the parameter as it appears in ALM.
    3. Enter the value you want to assign to this parameter.

...