getHeaders() {
33 |
34 | return RestXmlUtils.getAppXmlHeaders();
35 | }
36 | }
--------------------------------------------------------------------------------
/src/main/java/com/hp/application/automation/tools/sse/sdk/request/GetLabRunEntityDataRequest.java:
--------------------------------------------------------------------------------
1 | package com.hp.application.automation.tools.sse.sdk.request;
2 |
3 | import com.hp.application.automation.tools.sse.sdk.Client;
4 |
5 | /***
6 | *
7 | * @author Effi Bar-She'an
8 | * @author Dani Schreiber
9 | *
10 | */
11 |
12 | public class GetLabRunEntityDataRequest extends GetRequest {
13 |
14 | public GetLabRunEntityDataRequest(Client client, String runId) {
15 |
16 | super(client, runId);
17 | }
18 |
19 | @Override
20 | protected String getSuffix() {
21 |
22 | return String.format("procedure-runs/%s", _runId);
23 | }
24 | }
25 |
--------------------------------------------------------------------------------
/src/main/java/com/hp/application/automation/tools/sse/sdk/request/GetLabRunEntityTestSetRunsRequest.java:
--------------------------------------------------------------------------------
1 | package com.hp.application.automation.tools.sse.sdk.request;
2 |
3 | import com.hp.application.automation.tools.sse.sdk.Client;
4 |
5 | /***
6 | *
7 | * @author Effi Bar-She'an
8 | * @author Dani Schreiber
9 | *
10 | */
11 | public class GetLabRunEntityTestSetRunsRequest extends GetRequest {
12 |
13 | public GetLabRunEntityTestSetRunsRequest(Client client, String runId) {
14 |
15 | super(client, runId);
16 | }
17 |
18 | @Override
19 | protected String getSuffix() {
20 | return "procedure-testset-instance-runs";
21 | }
22 |
23 | @Override
24 | protected String getQueryString() {
25 |
26 | return String.format("query={procedure-run[%s]}&page-size=2000", _runId);
27 | }
28 |
29 | }
30 |
--------------------------------------------------------------------------------
/src/main/java/com/hp/application/automation/tools/sse/sdk/request/GetPCRunEntityDataRequest.java:
--------------------------------------------------------------------------------
1 | package com.hp.application.automation.tools.sse.sdk.request;
2 |
3 | import com.hp.application.automation.tools.sse.sdk.Client;
4 |
5 | /***
6 | *
7 | * @author Effi Bar-She'an
8 | * @author Dani Schreiber
9 | *
10 | */
11 |
12 | public class GetPCRunEntityDataRequest extends GetRequest {
13 |
14 | public GetPCRunEntityDataRequest(Client client, String runId) {
15 |
16 | super(client, runId);
17 | }
18 |
19 | @Override
20 | protected String getSuffix() {
21 |
22 | return String.format("runs/%s", _runId);
23 | }
24 | }
25 |
--------------------------------------------------------------------------------
/src/main/java/com/hp/application/automation/tools/sse/sdk/request/GetPCRunEntityTestSetRunsRequest.java:
--------------------------------------------------------------------------------
1 | package com.hp.application.automation.tools.sse.sdk.request;
2 |
3 | import com.hp.application.automation.tools.sse.sdk.Client;
4 |
5 | /***
6 | *
7 | * @author Effi Bar-She'an
8 | * @author Dani Schreiber
9 | *
10 | */
11 | public class GetPCRunEntityTestSetRunsRequest extends GetRequest {
12 |
13 | public GetPCRunEntityTestSetRunsRequest(Client client, String runId) {
14 |
15 | super(client, runId);
16 | }
17 |
18 | @Override
19 | protected String getSuffix() {
20 |
21 | return String.format("runs/%s", _runId);
22 | }
23 | }
24 |
--------------------------------------------------------------------------------
/src/main/java/com/hp/application/automation/tools/sse/sdk/request/GetRequest.java:
--------------------------------------------------------------------------------
1 | package com.hp.application.automation.tools.sse.sdk.request;
2 |
3 | import com.hp.application.automation.tools.sse.sdk.Client;
4 |
5 | /***
6 | *
7 | * @author Effi Bar-She'an
8 | * @author Dani Schreiber
9 | *
10 | */
11 |
12 | public abstract class GetRequest extends GeneralGetRequest {
13 |
14 | protected final String _runId;
15 |
16 | protected GetRequest(Client client, String runId) {
17 |
18 | super(client);
19 | _runId = runId;
20 | }
21 |
22 | }
23 |
--------------------------------------------------------------------------------
/src/main/java/com/hp/application/automation/tools/sse/sdk/request/GetRunEntityNameRequest.java:
--------------------------------------------------------------------------------
1 | package com.hp.application.automation.tools.sse.sdk.request;
2 |
3 | import com.hp.application.automation.tools.sse.sdk.Client;
4 |
5 | /***
6 | *
7 | * @author Effi Bar-She'an
8 | * @author Dani Schreiber
9 | *
10 | */
11 | public class GetRunEntityNameRequest extends GetRequest {
12 |
13 | private final String _nameSuffix;
14 |
15 | public GetRunEntityNameRequest(Client client, String suffix, String entityId) {
16 |
17 | super(client, entityId);
18 | _nameSuffix = suffix;
19 |
20 | }
21 |
22 | @Override
23 | protected String getSuffix() {
24 |
25 | return _nameSuffix;
26 | }
27 | }
28 |
--------------------------------------------------------------------------------
/src/main/java/com/hp/application/automation/tools/sse/sdk/request/PollSSERunRequest.java:
--------------------------------------------------------------------------------
1 | package com.hp.application.automation.tools.sse.sdk.request;
2 |
3 | import com.hp.application.automation.tools.sse.sdk.Client;
4 |
5 | /***
6 | *
7 | * @author Effi Bar-She'an
8 | * @author Dani Schreiber
9 | *
10 | */
11 |
12 | public class PollSSERunRequest extends GetRequest {
13 |
14 | private final String _runId;
15 |
16 | public PollSSERunRequest(Client client, String runId) {
17 |
18 | super(client, runId);
19 | _runId = runId;
20 | }
21 |
22 | @Override
23 | protected String getSuffix() {
24 |
25 | return String.format("procedure-runs/%s", _runId);
26 | }
27 | }
28 |
--------------------------------------------------------------------------------
/src/main/java/com/hp/application/automation/tools/sse/sdk/request/PostRequest.java:
--------------------------------------------------------------------------------
1 | package com.hp.application.automation.tools.sse.sdk.request;
2 |
3 | import com.hp.application.automation.tools.sse.sdk.Client;
4 |
5 | /***
6 | *
7 | * @author Effi Bar-She'an
8 | * @author Dani Schreiber
9 | *
10 | */
11 | public abstract class PostRequest extends GeneralPostRequest {
12 |
13 | protected final String _runId;
14 |
15 | protected PostRequest(Client client, String runId) {
16 |
17 | super(client);
18 | _runId = runId;
19 | }
20 |
21 | }
22 |
--------------------------------------------------------------------------------
/src/main/java/com/hp/application/automation/tools/sse/sdk/request/StopEntityRequest.java:
--------------------------------------------------------------------------------
1 | package com.hp.application.automation.tools.sse.sdk.request;
2 |
3 | import com.hp.application.automation.tools.sse.sdk.Client;
4 |
5 | /***
6 | *
7 | * @author Effi Bar-She'an
8 | * @author Dani Schreiber
9 | *
10 | */
11 |
12 | public class StopEntityRequest extends PostRequest {
13 |
14 | public StopEntityRequest(Client client, String runId) {
15 |
16 | super(client, runId);
17 | }
18 |
19 | @Override
20 | protected String getSuffix() {
21 |
22 | return String.format("procedure-runs/%s/stop", _runId);
23 | }
24 |
25 | }
26 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/model/AutEnvironmentModel/config.properties:
--------------------------------------------------------------------------------
1 | AlmServersAreNotDefined=HP ALM servers are not defined. To use this build step, goto Manage Jenkins->Configure System->Application Lifecycle Management->Add ALM server
2 |
3 | AutEnvironmentConfigurationDescription=Use this build step to assign values to AUT Environment Configuration in ALM.
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/model/AutEnvironmentModel/help-autEnvironmentId.html:
--------------------------------------------------------------------------------
1 |
2 | Assign ID of an AUT Environment that exists in the ALM project you selected.
3 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/model/AutEnvironmentModel/help-outputParameter.html:
--------------------------------------------------------------------------------
1 |
2 | The name of the build environment parameter that will get the ID of the updated/created AUT Environment
3 | Configuration.
4 | It then can be used as a parameter for following build steps.
5 |
6 | The parameter must be a String Parameter.
7 |
8 | If you named your parameter 'output_parameter' put here 'output_parameter' (exactly the same value).
9 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/model/AutEnvironmentModel/help-pathToJsonFile.html:
--------------------------------------------------------------------------------
1 |
2 | A path to the JSON file that will be loaded in order to assign values to all the AUT Environment Parameters of 'From
3 | JSON' type.
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/model/AutEnvironmentParameterModel/help-name.html:
--------------------------------------------------------------------------------
1 |
2 | The name must be set in the same hierarchical structure as it defined in ALM ( 'Parameters' tab of the AUT
3 | Environment)
4 |
5 | For example: 'Parameters/DB_Setting/Oracle/username'
6 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/model/AutEnvironmentParameterModel/help-paramType.html:
--------------------------------------------------------------------------------
1 |
2 | Manual - the value you'll assign for 'Parameter value' field will be used as is.
3 |
4 | Environmnet - the value you'll assign for 'Parameter value' will be looked for in the environment parameters and the
5 | resolved value will be used.
6 | If you named your parameter 'my_parameter' put here 'my_parameter' (exactly the same value).
7 |
8 | From JSON - the value you'll assign for 'Parameter value' will be looked for in the JSON file you specified for the
9 | 'Path to JSON file' entry.
10 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/model/AutEnvironmentParameterModel/help-value.html:
--------------------------------------------------------------------------------
1 |
2 | If you are using a 'From JSON' type, specify here the path for the element you would like to get.
3 |
4 | Make sure you are using
JsonPath style for defining it.
5 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/octane/actions/UFTTestDetectionPublisher/config.jelly:
--------------------------------------------------------------------------------
1 |
2 |
3 |
8 |
9 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/octane/actions/UFTTestDetectionPublisher/help-workspaceName.html:
--------------------------------------------------------------------------------
1 |
16 |
17 |
18 | Select Workspace name to assign the detected UFT tests to.
19 |
20 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/octane/actions/cucumber/CucumberTestResultsActionPublisher/config.jelly:
--------------------------------------------------------------------------------
1 |
17 |
18 |
19 |
20 |
21 |
23 |
24 |
25 |
26 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/octane/actions/cucumber/CucumberTestResultsActionPublisher/config.properties:
--------------------------------------------------------------------------------
1 | #
2 | # Copyright 2017 Hewlett-Packard Development Company, L.P.
3 | # Licensed under the Apache License, Version 2.0 (the "License");
4 | # you may not use this file except in compliance with the License.
5 | # You may obtain a copy of the License at
6 | #
7 | # http://www.apache.org/licenses/LICENSE-2.0
8 | #
9 | # Unless required by applicable law or agreed to in writing, software
10 | # distributed under the License is distributed on an "AS IS" BASIS,
11 | # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
12 | # See the License for the specific language governing permissions and
13 | # limitations under the License.
14 | #
15 | #
16 |
17 | description=\
18 | Fileset \u2018includes\u2019 \
19 | setting that specifies the generated cucumber XML report files, \
20 | such as \u2018myproject/target/cucumber-test-reports/*.xml\u2019. \
21 | Basedir of the fileset is the workspace root.
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/octane/actions/cucumber/CucumberTestResultsActionPublisher/help.html:
--------------------------------------------------------------------------------
1 |
16 |
17 |
18 | When using this action, Jenkins understands and reads the Cucumber test report XML structure.
19 | After reading the structure, Jenkins can provide useful information about Cucumber tests results to HPE ALM Octane.
20 |
21 |
22 | To use the feature, ensure that you have added a Publish JUnit test results post-build action to your build.
23 | Then, specify the path to the Cucumber report XML files in the Ant glob syntax.
24 | Be sure not to include any non-Cucumber-report files in this path. You can specify multiple patterns by separating them with commas.
25 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/octane/configuration/ConfigurationAction/index.properties:
--------------------------------------------------------------------------------
1 | #
2 | # Copyright 2017 Hewlett-Packard Development Company, L.P.
3 | # Licensed under the Apache License, Version 2.0 (the "License");
4 | # you may not use this file except in compliance with the License.
5 | # You may obtain a copy of the License at
6 | #
7 | # http://www.apache.org/licenses/LICENSE-2.0
8 | #
9 | # Unless required by applicable law or agreed to in writing, software
10 | # distributed under the License is distributed on an "AS IS" BASIS,
11 | # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
12 | # See the License for the specific language governing permissions and
13 | # limitations under the License.
14 | #
15 | #
16 |
17 | mqm.configuration.title=HPE ALM Octane Pipelines
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/pipelineSteps/LoadRunnerTestStep/config.properties:
--------------------------------------------------------------------------------
1 | DontForgetThePublisher=Make sure to enable the Publish HP \
2 | tests result option in the Post-build \
3 | Actions section. This allows the tests results to be published.
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/pipelineSteps/LoadRunnerTestStep/help-archiveTestResultsMode.html:
--------------------------------------------------------------------------------
1 |
2 | To view the run results, do one of the following:
3 | 1) In the left pane, click the Report and Summary link to display the report link and the link to the report folder. From this link, you can open the run results directly in your browser or open the artifacts
4 | 2) From the Build Artifacts:
5 | • Open the run_results.html to view the run results.
6 | • Download the zipped report to your desired location and unzip it. In the HP Run Results Viewer, select the Results.xml file found inside the unzipped folder.
7 | Note that this option is valid only when using the “Execute HP test from file system” build step.
8 |
9 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/pipelineSteps/LoadRunnerTestStep/help-controllerPollingInterval.html:
--------------------------------------------------------------------------------
1 |
2 | Polling interval for checking the scenario status, in seconds. The default is 30 seconds.
3 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/pipelineSteps/LoadRunnerTestStep/help-fsTests.html:
--------------------------------------------------------------------------------
1 |
2 | List of tests or folders that contain tests, to run. Each line should contain a single test, folder, or MTB file.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/pipelineSteps/LoadRunnerTestStep/help-fsTimeout.html:
--------------------------------------------------------------------------------
1 |
2 | Timeout value in seconds. If left empty, there is no timeout.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/pipelineSteps/LoadRunnerTestStep/help-ignoreErrorStrings.html:
--------------------------------------------------------------------------------
1 |
2 | Ignore errors during the scenario run containing any of the strings listed below. For example: "Error: CPU usage for this load generator has exceeded 80%"
3 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/pipelineSteps/LoadRunnerTestStep/help-perScenarioTimeOut.html:
--------------------------------------------------------------------------------
1 |
2 | The maximum time allotted for scenario execution, in minutes.
3 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/pipelineSteps/SseBuildAndPublishStep/config.properties:
--------------------------------------------------------------------------------
1 | DontForgetThePublisher=Don''t forget to enable the Publish HP \
2 | tests result option in the Post-build \
3 | Actions section so that the tests results are published.
4 |
5 | AlmServersAreNotDefined=HP ALM servers are not defined. To use this build step, goto Manage Jenkins->Configure System->Application Lifecycle Management->Add ALM server
6 |
7 | ServerSideTests=Use this build step to run ALM server-side functional test sets and Build Verification Suites.
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/pipelineSteps/SseBuildAndPublishStep/help-archiveTestResultsMode.html:
--------------------------------------------------------------------------------
1 |
2 | To view the run results, do one of the following:
3 | 1) In the left pane, click the Report and Summary link to display the report link and the link to the report folder. From this link, you can open the run results directly in your browser or open the artifacts
4 | 2) From the Build Artifacts:
5 | • Open the run_results.html to view the run results.
6 | • Download the zipped report to your desired location and unzip it. In the HP Run Results Viewer, select the Results.xml file found inside the unzipped folder.
7 | Note that this option is valid only when using the “Execute HP test from file system” build step.
8 |
9 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/pipelineSteps/SseBuildAndPublishStep/help-environmentConfigurationId.html:
--------------------------------------------------------------------------------
1 |
2 | To find the ID of your environment configuration, right-click the entity, copy the URL, and paste it to a text editor. Use the number associated with the EntityID at the end of the URL.
3 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/pipelineSteps/UftScenarioLoadStep/config.properties:
--------------------------------------------------------------------------------
1 | DontForgetThePublisher=Make sure to enable the Publish HP \
2 | tests result option in the Post-build \
3 | Actions section. This allows the tests results to be published.
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/pipelineSteps/UftScenarioLoadStep/help-archiveTestResultsMode.html:
--------------------------------------------------------------------------------
1 |
2 | To view the run results, do one of the following:
3 | 1) In the left pane, click the Report and Summary link to display the report link and the link to the report folder. From this link, you can open the run results directly in your browser or open the artifacts
4 | 2) From the Build Artifacts:
5 | • Open the run_results.html to view the run results.
6 | • Download the zipped report to your desired location and unzip it. In the HP Run Results Viewer, select the Results.xml file found inside the unzipped folder.
7 | Note that this option is valid only when using the “Execute HP test from file system” build step.
8 |
9 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/pipelineSteps/UftScenarioLoadStep/help-fsTests.html:
--------------------------------------------------------------------------------
1 |
2 | List of tests or folders that contain tests, to run. Each line should contain a single test, folder, or MTB file.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/results/PerformanceJobReportAction/index.jelly:
--------------------------------------------------------------------------------
1 |
9 |
10 |
12 |
13 |
14 |
15 | Job Performance Result
16 |
17 |
18 |
19 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/results/RunResultRecorder/help-archiveTestResultsMode.html:
--------------------------------------------------------------------------------
1 |
2 | To view the run results, do one of the following:
3 | 1) In the left pane, click the Report and Summary link to display the report link and the link to the report folder. From this link, you can open the run results directly in your browser or open the artifacts
4 | 2) From the Build Artifacts:
5 | • Open the run_results.html to view the run results.
6 | • Download the zipped report to your desired location and unzip it. In the HP Run Results Viewer, select the Results.xml file found inside the unzipped folder.
7 | Note that this option is valid only when using the “Execute HP test from file system” build step.
8 |
9 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/results/TestResultToALMUploader/config.properties:
--------------------------------------------------------------------------------
1 |
2 |
3 | AlmServersAreNotDefined=HP ALM servers are not defined. To use this build step, goto Manage Jenkins->Configure System->Application Lifecycle Management->Add ALM server
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/results/TestResultToALMUploader/help-almDomain.html:
--------------------------------------------------------------------------------
1 |
2 | The Domain of the project to be used.
3 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/results/TestResultToALMUploader/help-almPassword.html:
--------------------------------------------------------------------------------
1 |
2 | The password for the user to login.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/results/TestResultToALMUploader/help-almProject.html:
--------------------------------------------------------------------------------
1 |
2 | The project to be used.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/results/TestResultToALMUploader/help-almServerName.html:
--------------------------------------------------------------------------------
1 |
2 | The name of the ALM Server.
3 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/results/TestResultToALMUploader/help-almTestFolder.html:
--------------------------------------------------------------------------------
1 |
2 | The path of the test folder that will contain the uploaded test. The path doesn't include the Root test folder (Subject).
3 | For example, sampletestfolder\subfolder means, the tests will be uploaded to test folder named 'subfolder', which is under the test folder named 'sampletestfolder',
4 | and 'sampletestfolder' is under the root test folder 'Subject'.
5 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/results/TestResultToALMUploader/help-almTestSetFolder.html:
--------------------------------------------------------------------------------
1 |
2 | The path of the testset folder that will contain the uploaded testset. The path doesn't include the Root testset folder.
3 | For example, sampletestsetfolder\subfolder means, the testsets will be uploaded to testset folder named 'subfolder', which is under the testset folder named 'sampletestsetfolder',
4 | and 'sampletestsetfolder' is under the root testset folder 'Root'.
5 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/results/TestResultToALMUploader/help-almTimeout.html:
--------------------------------------------------------------------------------
1 |
2 | Number of seconds before timeout. If left empty timeout is unlimited.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/results/TestResultToALMUploader/help-almUserName.html:
--------------------------------------------------------------------------------
1 |
2 | The user name to login.
3 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/results/TestResultToALMUploader/help-jenkinsServerUrl.html:
--------------------------------------------------------------------------------
1 |
2 | The HTTP URL of the Jenkins Server, form example, http://myjenkinsserver.test.com:8080 .
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/results/TestResultToALMUploader/help-testingFramework.html:
--------------------------------------------------------------------------------
1 |
2 | The testing framework that is used when generate the testing result file.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/results/TestResultToALMUploader/help-testingResultFile.html:
--------------------------------------------------------------------------------
1 |
2 | The condition to find the testing result file, start from the root path of the job. For example, **/junitResult.xml to find testing result file for Junit Plugin, **/testng-results.xml to find testing result file for TestNG plugin.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/results/TestResultToALMUploader/help-testingTool.html:
--------------------------------------------------------------------------------
1 |
2 | The testing tool that is used when generate the testing result file.
3 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/AutEnvironmentBuilder/config.jelly:
--------------------------------------------------------------------------------
1 |
9 |
10 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/AutEnvironmentBuilder/config.properties:
--------------------------------------------------------------------------------
1 | AlmServersAreNotDefined=HP ALM servers are not defined. To use this build step, goto Manage Jenkins->Configure System->Application Lifecycle Management->Add ALM server
2 |
3 | AutEnvironmentConfigurationDescription=Use this build step to assign values to AUT Environment Configuration in ALM.
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/AutEnvironmentBuilder/help-environmentConfigurationId.html:
--------------------------------------------------------------------------------
1 |
2 | To find the ID of your environment configuration, right-click the entity, copy the URL, and paste it to a text editor. Use the number associated with the EntityID at the end of the URL.
3 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/PcBuilder/config.properties:
--------------------------------------------------------------------------------
1 | DontForgetThePublisher=Don''t forget to enable the Publish HP \
2 | tests result option in the Post-build \
3 | Actions section so that the tests results are published.
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/PcBuilder/help-pcServerName.html:
--------------------------------------------------------------------------------
1 |
2 | Hostname or IP address
3 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/PcBuilder/help-statusBySLA.html:
--------------------------------------------------------------------------------
1 |
2 | Check this option in order to set the build-step status according to a pre-defined SLA (Service Level Agreement) configured within your performance test.
3 | Unless checked, the build-step will be labeled as Passed as long as no failures occurred.
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/PcBuilder/help-testInstanceId.html:
--------------------------------------------------------------------------------
1 |
2 | Represents an instance of a performance test within an ALM Test Set. In order to find the test instance id go to: PC Web UI > Test Lab perspective > Performance Test Set table and look for the ID column
3 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/PcBuilder/help-vudsMode.html:
--------------------------------------------------------------------------------
1 |
2 | A Virtual User Day (VUD) license provides you with a specified number of Vusers (VUDs) that you can run an unlimited number of times within a 24 hour period.
3 | Before using this option, make sure that VUDs licenses are applied in your HP Performance Center environment.
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/RunFromAlmBuilder/config.properties:
--------------------------------------------------------------------------------
1 | DontForgetThePublisher=Don''t forget to enable the Publish HP \
2 | tests result option in the Post-build \
3 | Actions section so that the tests results are published.
4 |
5 | AlmServersAreNotDefined=HP ALM servers are not defined. To use this build step, goto Manage Jenkins->Configure System->Application Lifecycle Management->Add ALM server
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/RunFromAlmBuilder/help-AlmRunHost.html:
--------------------------------------------------------------------------------
1 |
2 | If the Run mode field is set to Run remotely, use this field to specify the name of the host that runs the test set.
3 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/RunFromAlmBuilder/help-AlmRunMode.html:
--------------------------------------------------------------------------------
1 |
2 | Defines how the test set is executed:
3 |
4 | - Run locally: The test set is run on the machine that performs the build.
5 | - Run remotely: The test set is run on the host defined in the Testing Tool host field.
6 | - Run on planned host: The test set is run on the host defined in ALM.
7 |
8 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/RunFromAlmBuilder/help-AlmTestSets.html:
--------------------------------------------------------------------------------
1 |
2 | List of test sets to run. Each line contains a path to a test set or a test set folder.
3 | For example: Root\subFolder1\subFolder2\testSetToRun
4 |
5 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/RunFromAlmBuilder/help-AlmTimeout.html:
--------------------------------------------------------------------------------
1 |
2 | Number of seconds before timeout. If left empty timeout is unlimited.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/RunFromFileBuilder/config.properties:
--------------------------------------------------------------------------------
1 | DontForgetThePublisher=Make sure to enable the Publish HP \
2 | tests result option in the Post-build \
3 | Actions section. This allows the tests results to be published.
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/RunFromFileBuilder/help-controllerPollingInterval.html:
--------------------------------------------------------------------------------
1 |
2 | Polling interval for checking the scenario status, in seconds. The default is 30 seconds.
3 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/RunFromFileBuilder/help-fsAppParamName.html:
--------------------------------------------------------------------------------
1 |
2 | The parameter name of object identifier, as defined in the UFT script.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/RunFromFileBuilder/help-fsAppPath.html:
--------------------------------------------------------------------------------
1 |
2 | The path of the application to upload to Mobile Center, on the Jenkins master machine.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/RunFromFileBuilder/help-fsPassword.html:
--------------------------------------------------------------------------------
1 |
2 | The password for Mobile Center.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/RunFromFileBuilder/help-fsProxyAddress.html:
--------------------------------------------------------------------------------
1 |
2 | Example: 16.54.185.180:8080
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/RunFromFileBuilder/help-fsTests.html:
--------------------------------------------------------------------------------
1 |
2 | List of tests or folders that contain tests, to run. Each line should contain a single test, folder, or MTB file.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/RunFromFileBuilder/help-fsTimeout.html:
--------------------------------------------------------------------------------
1 |
2 | Timeout value in seconds. If left empty, there is no timeout.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/RunFromFileBuilder/help-fsUserName.html:
--------------------------------------------------------------------------------
1 |
2 | The user name for Mobile Center.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/RunFromFileBuilder/help-ignoreErrorStrings.html:
--------------------------------------------------------------------------------
1 |
2 | Ignore errors during the scenario run containing any of the strings listed below. For example: "Error: CPU usage for this load generator has exceeded 80%"
3 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/RunFromFileBuilder/help-mcServerName.html:
--------------------------------------------------------------------------------
1 |
2 | The Mobile Center host.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/RunFromFileBuilder/help-perScenarioTimeOut.html:
--------------------------------------------------------------------------------
1 |
2 | The maximum time allotted for scenario execution, in minutes.
3 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/SseBuilder/config.properties:
--------------------------------------------------------------------------------
1 | DontForgetThePublisher=Don''t forget to enable the Publish HP \
2 | tests result option in the Post-build \
3 | Actions section so that the tests results are published.
4 |
5 | AlmServersAreNotDefined=HP ALM servers are not defined. To use this build step, goto Manage Jenkins->Configure System->Application Lifecycle Management->Add ALM server
6 |
7 | ServerSideTests=Use this build step to run ALM server-side functional test sets and Build Verification Suites.
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/SseBuilder/help-environmentConfigurationId.html:
--------------------------------------------------------------------------------
1 |
2 | To find the ID of your environment configuration, right-click the entity, copy the URL, and paste it to a text editor. Use the number associated with the EntityID at the end of the URL.
3 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/SvChangeModeBuilder/config.properties:
--------------------------------------------------------------------------------
1 | # suppress inspection "UnusedProperty"
2 | NoSvServerDefined=No HPE Service Virtualization server is defined. To use this build step, goto Manage Jenkins->Configure System->Service Virtualization->Add SV server
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/SvChangeModeBuilder/help-force.html:
--------------------------------------------------------------------------------
1 |
2 | If set, service will be modified regardless it is locked by another user.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/SvDeployBuilder/config.properties:
--------------------------------------------------------------------------------
1 | # suppress inspection "UnusedProperty"
2 | NoSvServerDefined=No HPE Service Virtualization server is defined. To use this build step, goto Manage Jenkins->Configure System->Service Virtualization->Add SV server
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/SvDeployBuilder/help-firstAgentFallback.html:
--------------------------------------------------------------------------------
1 |
2 | Use first agent of the same type if no agent with id referenced from virtual service exists on target server.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/SvDeployBuilder/help-force.html:
--------------------------------------------------------------------------------
1 |
2 | If set, service will be redeployed regardless it is locked by another user.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/SvDeployBuilder/help-service.html:
--------------------------------------------------------------------------------
1 |
2 | Name or ID of service to be deployed. All services from project are deployed if no service is specified.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/SvExportBuilder/config.properties:
--------------------------------------------------------------------------------
1 | # suppress inspection "UnusedProperty"
2 | NoSvServerDefined=No HPE Service Virtualization server is defined. To use this build step, goto Manage Jenkins->Configure System->Service Virtualization->Add SV server
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/SvExportBuilder/help-cleanTargetDirectory.html:
--------------------------------------------------------------------------------
1 |
2 | If checked, all direct subfolders of target directory containing a project file (*.vproj) will be deleted before export.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/SvExportBuilder/help-force.html:
--------------------------------------------------------------------------------
1 |
2 | If set, service will be modified regardless it is locked by another user.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/SvExportBuilder/help-switchToStandByFirst.html:
--------------------------------------------------------------------------------
1 |
2 | Switch service to Stand-By mode to finish current learning before exporting learned data.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/SvExportBuilder/help-targetDirectory.html:
--------------------------------------------------------------------------------
1 |
2 | Directory where exported services will be written.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/SvUndeployBuilder/config.properties:
--------------------------------------------------------------------------------
1 | # suppress inspection "UnusedProperty"
2 | NoSvServerDefined=No HPE Service Virtualization server is defined. To use this build step, goto Manage Jenkins->Configure System->Service Virtualization->Add SV server
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/SvUndeployBuilder/help-continueIfNotDeployed.html:
--------------------------------------------------------------------------------
1 |
2 | Don't fail if any service marked to be undeployed is not deployed on server.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/SvUndeployBuilder/help-force.html:
--------------------------------------------------------------------------------
1 |
2 | If set, service will be undeployed regardless it is locked by another user.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/run/UploadAppBuilder/config.properties:
--------------------------------------------------------------------------------
1 | McServersAreNotDefined=HP MC servers are not defined. To use this build step, goto Manage Jenkins->Configure System->Mobile Center->Add MC server
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/settings/AlmServerSettingsBuilder/help-almServerName.html:
--------------------------------------------------------------------------------
1 |
2 | The name of the ALM Server. This will be used in the "Execute HP functional test from ALM" build step configuration.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/settings/AlmServerSettingsBuilder/help-almServerUrl.html:
--------------------------------------------------------------------------------
1 |
2 | The name of the URL of the ALM Server: http://myalmserver:8080/qcbin
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/settings/AlmServerSettingsBuilder/help-almServerVersion.html:
--------------------------------------------------------------------------------
1 |
2 | The version of the ALM server:10.0, 11.0, 11.5
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/settings/MCServerSettingsBuilder/global.jelly:
--------------------------------------------------------------------------------
1 |
2 |
3 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 |
38 |
39 |
40 |
41 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/settings/MCServerSettingsBuilder/help-mcServerName.html:
--------------------------------------------------------------------------------
1 |
2 | The name of the MC Server.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/settings/MCServerSettingsBuilder/help-mcServerUrl.html:
--------------------------------------------------------------------------------
1 |
2 | The Mobile Center host. i.e: http://mcserver:8080
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/settings/OctaneServerSettingsBuilder/global.properties:
--------------------------------------------------------------------------------
1 | global.config.description=HPE ALM Octane CI Plugin
2 | global.config.server.title=HPE ALM Octane Server Configuration
3 | global.config.location.title=Location
4 | global.config.location.description=Location of the HPE ALM Octane application
5 | global.config.domain.title=Domain
6 | global.config.domain.description=Domain name
7 | global.config.project.title=Project
8 | global.config.project.description=Project name
9 | global.config.username.title=Client ID
10 | global.config.username.description=Client ID used for logging into the ALM Octane server
11 | global.config.password.title=Client secret
12 | global.config.password.description=Client secret used for logging into the ALM Octane server
13 | global.config.test.connection=Test Connection
14 | global.config.test.connection.progress=Connecting the ALM Octane server...
15 | global.config.impersonatedUser.title=Jenkins user
16 | global.config.impersonatedUser.description=The user to impersonate (Jobs will be executed on behalf of this user)
17 |
18 | global.config.dynamic.instanceId.title=Show plugin instance id
19 | global.config.instanceId.title=Instance id
20 | global.config.instanceId.description=An ID to uniquely identify this instance of the plugin.
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/settings/OctaneServerSettingsBuilder/help-identity.html:
--------------------------------------------------------------------------------
1 |
2 | In ALM Octane, a pipeline’s unique identification includes this ID.
3 | When should I change this value?
4 |
5 | - When you install the HP Application Automation Tools plugin instead of the HPE ALM Octane CI plugin. To enable this plugin to work with existing pipelines, change the instance ID to the one used by your pipelines in ALM Octane (Settings > DevOps > CI servers, “Instance ID” column).
6 |
7 | - If you duplicate your Jenkins installation. Change the instance ID (in any way) to prevent results reported from the new copy of the plugin from being mixed in ALM Octane with results reported from the original one.
To separately collect information from the new copy, create new pipelines.
8 |
9 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/settings/OctaneServerSettingsBuilder/help-impersonatedUser.html:
--------------------------------------------------------------------------------
1 |
2 | The Jenkins user's account is used to run jobs that ALM Octane runs.
3 |
Notes:
4 |
5 | -
6 | Make sure the user exists in Jenkins.
7 |
8 | -
9 | We strongly recommend specifying a Jenkins user for ALM Octane. Set this user's permissions to the minimum required for this integration: Job Build permissions.
10 |
11 | -
12 | If you do not specify a Jenkins user, ALM Octane uses the Anonymous user, and is limited to Anonymous's user permissions.
13 |
14 |
15 |
16 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/settings/OctaneServerSettingsBuilder/help-uiLocation.html:
--------------------------------------------------------------------------------
1 |
2 | Login into the ALM Octane application and copy & paste the location from your browser.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/com/hp/application/automation/tools/settings/OctaneServerSettingsBuilder/help-username.html:
--------------------------------------------------------------------------------
1 |
2 | Obtain a Client ID and Client secret from ALM Octane configuration.
3 |
4 |
--------------------------------------------------------------------------------
/src/main/resources/index.jelly:
--------------------------------------------------------------------------------
1 |
4 |
5 |
6 | This plugin enables integration with HPE products, such as: ALM, ALM Octane, Unified Functional Testing, LoadRunner, and Performance Center.
7 |
8 |
--------------------------------------------------------------------------------
/src/main/resources/lib/octane/menu-button-arrow.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/hpsa/hpe-application-automation-tools-plugin/987536f5551bc76fd028d746a951d1fd72c7567a/src/main/resources/lib/octane/menu-button-arrow.png
--------------------------------------------------------------------------------
/src/main/webapp/PerformanceReport/LoadRunner.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/hpsa/hpe-application-automation-tools-plugin/987536f5551bc76fd028d746a951d1fd72c7567a/src/main/webapp/PerformanceReport/LoadRunner.png
--------------------------------------------------------------------------------
/src/main/webapp/autEnvironment.js:
--------------------------------------------------------------------------------
1 | /**
2 | * Created by barush on 09/11/2014.
3 | */
4 |
5 | function checkCorrespondingCheckbox(e) {
6 |
7 | var parentTableNode = getAncestorByTagName(e, 'table');
8 | var nearestCheckbox = parentTableNode.getElementsByClassName('autEnvParameterCheckbox')[0];
9 |
10 | if (e.value === 'From JSON') {
11 | nearestCheckbox.style.display = 'inline';
12 | } else {
13 | nearestCheckbox.style.display = 'none';
14 | }
15 | }
16 |
17 | function updateValuesOnLoad() {
18 | var elementsByClassName = document.getElementsByClassName('autEnv');
19 | var i;
20 | for (i = 0; elementsByClassName.length > i; i++) {
21 | checkCorrespondingCheckbox(elementsByClassName[i]);
22 | }
23 | }
24 |
25 | function getAncestorByTagName(el, tn) {
26 | tn = tn.toLowerCase();
27 | if (el.parentNode) {
28 | if (el.parentNode.nodeType == 1
29 | && el.parentNode.tagName.toLowerCase() == tn
30 | ) return el.parentNode;
31 | return getAncestorByTagName(el.parentNode, tn);
32 | }
33 | return null
34 | }
35 |
36 |
37 | setTimeout(updateValuesOnLoad(), 0);
38 |
39 |
--------------------------------------------------------------------------------
/src/main/webapp/help/accessKey.html:
--------------------------------------------------------------------------------
1 | Obtain a Client ID and Client secret from ALM Octane configuration.
2 |
3 |
4 |
--------------------------------------------------------------------------------
/src/main/webapp/help/impersonatedUser.html:
--------------------------------------------------------------------------------
1 | The Jenkins user's account is used to run jobs that ALM Octane runs.
2 | Notes:
3 |
4 | -
5 | Make sure the user exists in Jenkins.
6 |
7 | -
8 | We strongly recommend specifying a Jenkins user for ALM Octane. Set this user's permissions to the minimum required for this integration: Job Build permissions.
9 |
10 | -
11 | If you do not specify a Jenkins user, ALM Octane uses the Anonymous user, and is limited to Anonymous's user permissions.
12 |
13 |
14 |
15 |
16 |
--------------------------------------------------------------------------------
/src/main/webapp/help/uiLocation.html:
--------------------------------------------------------------------------------
1 | Login into the ALM Octane application and copy & paste the location from your browser.
--------------------------------------------------------------------------------
/src/main/webapp/icons/16x16/failed.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/hpsa/hpe-application-automation-tools-plugin/987536f5551bc76fd028d746a951d1fd72c7567a/src/main/webapp/icons/16x16/failed.png
--------------------------------------------------------------------------------
/src/main/webapp/icons/16x16/html_report.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/hpsa/hpe-application-automation-tools-plugin/987536f5551bc76fd028d746a951d1fd72c7567a/src/main/webapp/icons/16x16/html_report.png
--------------------------------------------------------------------------------
/src/main/webapp/icons/16x16/passed.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/hpsa/hpe-application-automation-tools-plugin/987536f5551bc76fd028d746a951d1fd72c7567a/src/main/webapp/icons/16x16/passed.png
--------------------------------------------------------------------------------
/src/main/webapp/icons/16x16/rrv_report.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/hpsa/hpe-application-automation-tools-plugin/987536f5551bc76fd028d746a951d1fd72c7567a/src/main/webapp/icons/16x16/rrv_report.png
--------------------------------------------------------------------------------
/src/main/webapp/icons/16x16/stop.ico:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/hpsa/hpe-application-automation-tools-plugin/987536f5551bc76fd028d746a951d1fd72c7567a/src/main/webapp/icons/16x16/stop.ico
--------------------------------------------------------------------------------
/src/main/webapp/icons/16x16/stop.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/hpsa/hpe-application-automation-tools-plugin/987536f5551bc76fd028d746a951d1fd72c7567a/src/main/webapp/icons/16x16/stop.png
--------------------------------------------------------------------------------
/src/main/webapp/icons/24x24/failed.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/hpsa/hpe-application-automation-tools-plugin/987536f5551bc76fd028d746a951d1fd72c7567a/src/main/webapp/icons/24x24/failed.png
--------------------------------------------------------------------------------
/src/main/webapp/icons/24x24/html_report.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/hpsa/hpe-application-automation-tools-plugin/987536f5551bc76fd028d746a951d1fd72c7567a/src/main/webapp/icons/24x24/html_report.png
--------------------------------------------------------------------------------
/src/main/webapp/icons/24x24/passed.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/hpsa/hpe-application-automation-tools-plugin/987536f5551bc76fd028d746a951d1fd72c7567a/src/main/webapp/icons/24x24/passed.png
--------------------------------------------------------------------------------
/src/main/webapp/icons/24x24/rrv_report.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/hpsa/hpe-application-automation-tools-plugin/987536f5551bc76fd028d746a951d1fd72c7567a/src/main/webapp/icons/24x24/rrv_report.png
--------------------------------------------------------------------------------
/src/main/webapp/icons/24x24/uft_report.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/hpsa/hpe-application-automation-tools-plugin/987536f5551bc76fd028d746a951d1fd72c7567a/src/main/webapp/icons/24x24/uft_report.png
--------------------------------------------------------------------------------
/src/main/webapp/js/libaries/react/react-dom.js:
--------------------------------------------------------------------------------
1 | /**
2 | * ReactDOM v15.3.2
3 | *
4 | * Copyright 2013-present, Facebook, Inc.
5 | * All rights reserved.
6 | *
7 | * This source code is licensed under the BSD-style license found in the
8 | * LICENSE file in the root directory of this source tree. An additional grant
9 | * of patent rights can be found in the PATENTS file in the same directory.
10 | *
11 | */
12 | // Based off https://github.com/ForbesLindesay/umd/blob/master/template.js
13 | ;(function(f) {
14 | // CommonJS
15 | if (typeof exports === "object" && typeof module !== "undefined") {
16 | module.exports = f(require('react'));
17 |
18 | // RequireJS
19 | } else if (typeof define === "function" && define.amd) {
20 | define(['react'], f);
21 |
22 | //