...

This operation will execute on all of the selected endpoints and will execute on each of the selected endpoints.

Additional Configuration Information

Credential information or other data for your test cases is often passed at runtime to address security concerns or because values may change frequently. This ensures that test cases don't need to be modified after they've been created. To simplify this process, Opkey provides the option to pass these values using a command called --global variable.

Now, let's take a look at an example of how this can be used in FlexDeploy.

Before you execute the test suite, ensure that you have created global variables in Opkey, such as FSMUserName,FSMPassword, which can be mapped to your test case. These global variables are declared within Opkey and allow you to pass values dynamically at runtime during the execution.

For instance, FSMUserName,FSMPassword could be a global variables that stores a user’s login info, which will be referenced in your test case.

...

Using global variables in FlexDeploy Opkey Plugin

The FlexDeploy Opkey Plugin (runOpkeyTest operation)has a input option called Additional Arguments, which enables you to pass extra commands or parameters to the Opkey test during execution. You can specify these additional arguments in FlexDeploy while triggering the test.

For example, you can pass the global variable FSMUserName,FSMPasswordas a runtime parameter, allowing the test suite to dynamically use the value assigned to FSMUserNameand FSMPassword

Example 1

FlexDeploy enables secure passing of dynamic values, such as FSMUserName and FSMPassword, by referencing either Target Group Properties or Integration Instance Properties. In FlexDeploy YAML configuration, Groovy evaluates these values first before they are passed into the test workflow. This allows you to use the current target properties directly without qualifications, simplifying the process. However, when dealing with sensitive information like password properties, you do not want them to be evaluated. Instead, these values should be passed as environment variables, which requires qualifying the property with either the Target Group Code or Integration Instance Code, depending on where the property is located.

For example, if you have a Cloud Account configured in FlexDeploy with properties for username and password, you can dynamically reference these properties and concatenate them with the Target Group account code. This approach ensures that credentials are securely passed during test or deployment execution without exposing sensitive information.

For Windows

---
testName: Opkey Demo
description: Generated Opkey Test
workflow:
  name: Opkey-runOpkeyTests
  inputs:
    - code: OPKEY_INP_PROJECT_NAME
      value: Flexagon
    - code: OPKEY_INP_TEST_SUITE_PATH
      value: 'Project Workspace/FSM/FSM Validate'
    - code: OPKEY_INP_AGENT_NAME
      value: utlwt01
    - code: OPKEY_INP_PLUGIN_NAME
      value: OracleFusion
    - code: OPKEY_INP_ADDITIONAL_ARGUMENTS
      groovy: TRUE
      value: '"--global-variable FSMUserName=%" + FDFSM_CLOUD_ACCOUNT_CODE + "_FDFSMACCT_USERNAME%,FSMPassword=%" + FDFSM_CLOUD_ACCOUNT_CODE + "_FDFSMACCT_PASSWORD%"'
    - code: TEST_INSTANCE
      value: OPKEYTEST    

For Linux

---
testName: Opkey Demo
description: Generated Opkey Test
workflow:
  name: Opkey-runOpkeyTests
  inputs:
    - code: OPKEY_INP_PROJECT_NAME
      value: Flexagon
    - code: OPKEY_INP_TEST_SUITE_PATH
      value: 'Project Workspace\FSM\FSM Validate'
    - code: OPKEY_INP_AGENT_NAME
      value: utlwt01
    - code: OPKEY_INP_PLUGIN_NAME
      value: OracleFusion
    - code: OPKEY_INP_ADDITIONAL_ARGUMENTS
      groovy: TRUE
      value: '"--global-variable FSMUserName=\$" + FDFSM_CLOUD_ACCOUNT_CODE + "_FDFSMACCT_USERNAME,FSMPassword=\$" + FDFSM_CLOUD_ACCOUNT_CODE + "_FDFSMACCT_PASSWORD"'
    - code: TEST_INSTANCE
      value: OPKEYTEST      

Test-Suite Execution Guide

Opkey Test Suite Execution Guide Additional Configuration Information