customatics / leaptest-plugin Goto Github PK

View Code? Open in Web Editor NEW

2.0 2.0 5.0 4.05 MB

This is Leaptest plugin for Jenkins

License: MIT License

Java 87.51% HTML 2.79% JavaScript 9.70%

leaptest-plugin's People

Contributors

Stargazers

Watchers

Forkers

sunderfield robinong79 campanda romanchetto praqma

leaptest-plugin's Issues

[3.0.0] Do not print test case std-out for Passed case, as it makes Junit plugin fail the case in reporting

[BUG] Incorrect schedule variable value if it contains variable regex separator in "value" part

If try to add the next schedule variable: URL:https://example.com the plugin creates URL : https key value pair, ignoring //example.com part of value.

This occurs due to this part of code:

leaptest-plugin/src/main/java/com/customatics/leaptest_plugin/PluginHandler.java

Lines 52 to 58 in 2f39814

    
           String[] splittedKeyAndValue = rawKeyValuePair.split(variableSeparatorRegex); 
        
           if(splittedKeyAndValue.length < 2){ 
        
               listener.getLogger().println(String.format(Messages.INVALID_SCHEDULE_VARIABLE,rawKeyValuePair)); 
        
               continue; 
        
           } 
        
           String key = splittedKeyAndValue[0]; 
        
           String value = splittedKeyAndValue[1];

Array splittedKeyAndValue contains 3 elements in this case, were 3rd one contains missed //example.com

[3.0.0] Add wait until run is ready to monitor

Before

...
The schedule status is already 'Executing' - Cannot start, try again in 1.99555 minutes
The schedule is ready to run as the state is: 'Finished' - wait for 0.2544166666666667 minutes
//////////////////////////////////////////////////////////////////////////////////////
Schedule XXX.dk smoketest - afviklermaskine - XXX.dk[e6683b12-2ddb-4b9b-853f-c4fa18908e3b] Launched Successfully!
ERROR: Leapwork for Jenkins plugin finished with errors!
ERROR: Code: 404 Status: Run with id e6683b12-2ddb-4b9b-853f-c4fa18908e3b not found!
No such run e6683b12-2ddb-4b9b-853f-c4fa18908e3b !
...

After:

...
The schedule status is already 'Executing' - wait a minute...
The schedule is ready to run as the state is: 'Finished' - let's go
//////////////////////////////////////////////////////////////////////////////////////
Schedule XXXX smoketest - afviklermaskine - XXX.dk[e6683b12-2ddb-4b9b-853f-c4fa18908e3b] Launched Successfully!
RunId: 'e9f3a245-8869-4bf9-a3cc-b95d25a30699' is not ready yet - wait a sec
RunId: 'e9f3a245-8869-4bf9-a3cc-b95d25a30699' is not ready yet - wait a sec
RunId: 'e9f3a245-8869-4bf9-a3cc-b95d25a30699' is not ready yet - wait a sec
RunId: 'e9f3a245-8869-4bf9-a3cc-b95d25a30699' is not ready yet - wait a sec
RunId: 'e9f3a245-8869-4bf9-a3cc-b95d25a30699' is ready to monitor
----------------------------------------------------------------------------------------
RunItem: TTS-1331 Kunde-pc | Status: Passed | Elapsed: 7.2260848
...

Jenkins Core 2.19.4 does not work with JUnit plugin for manual testing/debugging - required version 2.60.3

[3.0.0] More schedules configured - issue is that it is executed in reverse order

13:53:28 ....
13:53:28 Schedule  XXX [cec76e11-ec90-4b58-841a-b265fe7ce4e1] successfully detected!
13:53:28 Schedule YYY [3fb945e5-1152-4162-ba84-d6f42c12f265] successfully detected!
13:53:28 The schedule is ready to run as the state is: 'Finished' - let's go
13:53:28 //////////////////////////////////////////////////////////////////////////////////////
13:53:28 Schedule YYY [3fb945e5-1152-4162-ba84-d6f42c12f265] Launched Successfully!
13:53:29 RunId: 'f20e1222-7b63-48c6-b74d-3be73a0f64a2' is not ready yet - wait a minute

[3.1.0] Access key should not be displayed in console output log

....
LEAPWORK controller hostname: 10.139.51.141
LEAPWORK controller port: 9001
LEAPWORK controller Access Key: asdasdf7a453   <--- REMOVE
JUnit report file name: reports.xml
...

Add global configuration for available LeapWork Controllers for job to use Configuration-as-Code plugin

Being able to roll this plugin out preconfigured on to multiple Jenkins instances, it'd be great if the plugin could be updated/altered/fixed to be compliant "the standard Jenkins way" so it can be configured via the plugin Configuration-as-code plugin

[FEATURE-REQ] Use environment variable expansion in configuration of controllers and schedules

This would make it Matrix-build type and parameterized build compliant

[3.0.0] Show more detailed information about Errors and/or invalid schedules

see #18 for configuration

14:27:00 2018-11-16T13:27:00.4447994+00:00 - Case is passed.
14:27:00 Environment: Azure agent
14:27:00 Schedule: XXX
14:27:01 There were detected 'ERRORS' or 'INVALID SCHEDULES' hence set the build status='FAILURE'
14:27:01 Leapwork for Jenkins  plugin  successfully finished!
14:27:01 Build step 'Leapwork Integration' changed build result to FAILURE

[3.0.0] Add "wait" until schedule is ready for running

The new LeapWork does not have a "queue"-ing mechanism. The "plugin" will fail as the returned "runID" does not exist..

It makes the setup more resilient in the a-sync Jenkins setup

[3.1.0] JobDSL : leapworkWritePassedFlowKeyFrames is advanced, but mandatory for JobDSL

This advanced setting is mandatory for JobDSL - Create it with default value

      leapworkWritePassedFlowKeyFrames(false)

This is processing without it specified

Processing provided DSL script
ERROR: (script, line 3) the following options are required and must be specified: leapworkWritePassedFlowKeyFrames
Finished: FAILURE

Changing the report file name does not work - keeps reloading default

Report is not generated due to workspace path

Hi, I am using leaptest plugin 3.1.1 on jenkins 2.176.2 on windows 10 and I am not able to create a report.

In the console output I get:
...
JUnit report file name: report.xml
Workspace: /c:/build/something/DEV/
...
ERROR: Illegal char <:> at index 2: /c:/build/something/DEV/\report.xml

I have no idea why a / is added in front of the workspace path.

Thank you in advance.
Mieke

Toggle of status on failed test cases does not work

The usage and implementation of the status setting does not work nor implemented. Make the default to be success as the JUnit plugin will parse and verdict the test cases according to for example "total" and "new" and set the status accordingly.

In case of failed execution it should throw an abort exception and the platform sets the status to failure

Make the plugin compile out to the box. Update to 2.x Jenkins and dependencies

Configure leapwork plugin on a https-based jenkins

Hello

I'm in the middle of configuring the leapwork-plugin on a new Jenkins. However when I set up a job and click "select schedules" I receive a general browser error, saying the either my url, accesskey or something else is wrong. I've checked the developer-extensions and find that i'm running into a "Same-origin" policy issue. I have tried to install the CORS plugin and configure it, but since leapwork is running http and jenkins is on https it does not work.

Does anybody else have this issue?

[3.1.0] Does not compile out-of-the-box due to "enforcer" dependency errors

[INFO] Scanning for projects...
[WARNING] The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:2.1 is missing, no dependency information available
[WARNING] Failed to build parent project for org.jenkins-ci.plugins:leaptest-plugin:hpi:3.1.0
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Leapwork Integration 3.1.0
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-hpi-plugin:2.1:validate (default-validate) @ leaptest-plugin ---
[INFO] 
[INFO] --- maven-enforcer-plugin:3.0.0-M1:display-info (display-info) @ leaptest-plugin ---
[INFO] Maven Version: 3.3.9
[INFO] JDK Version: 1.8.0_191 normalized as: 1.8.0-191
[INFO] OS Info: Arch: amd64 Family: windows Name: windows 10 Version: 10.0
[INFO] 
[INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (display-info) @ leaptest-plugin ---
[INFO] Ignoring requireUpperBoundDeps in com.google.guava:guava
[WARNING] Rule 5: org.apache.maven.plugins.enforcer.RequireUpperBoundDeps failed with message:
Failed while enforcing RequireUpperBoundDeps. The error(s) are [
Require upper bound dependencies error for org.apache.ant:ant:1.8.4 paths to dependency are:
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-core:2.60.3
    +-org.apache.ant:ant:1.8.4
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.lib:lib-jenkins-maven-embedder:3.11
      +-org.apache.ant:ant:1.9.2
, 
Require upper bound dependencies error for org.eclipse.jetty:jetty-util:9.2.12.v20150709 paths to dependency are:
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.main:jenkins-test-harness-htmlunit:2.18-1
      +-org.eclipse.jetty:jetty-util:9.2.12.v20150709
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.eclipse.jetty:jetty-webapp:9.2.15.v20160210
      +-org.eclipse.jetty:jetty-xml:9.2.15.v20160210
        +-org.eclipse.jetty:jetty-util:9.2.15.v20160210
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.main:jenkins-test-harness-htmlunit:2.18-1
      +-org.eclipse.jetty.websocket:websocket-client:9.2.12.v20150709
        +-org.eclipse.jetty:jetty-util:9.2.12.v20150709
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.main:jenkins-test-harness-htmlunit:2.18-1
      +-org.eclipse.jetty:jetty-io:9.2.12.v20150709
        +-org.eclipse.jetty:jetty-util:9.2.12.v20150709
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.main:jenkins-test-harness-htmlunit:2.18-1
      +-org.eclipse.jetty.websocket:websocket-common:9.2.12.v20150709
        +-org.eclipse.jetty:jetty-util:9.2.12.v20150709
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.eclipse.jetty:jetty-security:9.2.15.v20160210
      +-org.eclipse.jetty:jetty-server:9.2.15.v20160210
        +-org.eclipse.jetty:jetty-http:9.2.15.v20160210
          +-org.eclipse.jetty:jetty-util:9.2.15.v20160210
, 
Require upper bound dependencies error for org.eclipse.jetty:jetty-io:9.2.12.v20150709 paths to dependency are:
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.main:jenkins-test-harness-htmlunit:2.18-1
      +-org.eclipse.jetty:jetty-io:9.2.12.v20150709
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.eclipse.jetty:jetty-security:9.2.15.v20160210
      +-org.eclipse.jetty:jetty-server:9.2.15.v20160210
        +-org.eclipse.jetty:jetty-io:9.2.15.v20160210
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.main:jenkins-test-harness-htmlunit:2.18-1
      +-org.eclipse.jetty.websocket:websocket-client:9.2.12.v20150709
        +-org.eclipse.jetty:jetty-io:9.2.12.v20150709
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.main:jenkins-test-harness-htmlunit:2.18-1
      +-org.eclipse.jetty.websocket:websocket-common:9.2.12.v20150709
        +-org.eclipse.jetty:jetty-io:9.2.12.v20150709
, 
Require upper bound dependencies error for org.codehaus.plexus:plexus-utils:2.1 paths to dependency are:
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.eclipse.sisu:org.eclipse.sisu.plexus:0.1.0
      +-org.codehaus.plexus:plexus-utils:2.1
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.lib:lib-jenkins-maven-embedder:3.11
      +-org.apache.maven:maven-core:3.1.0
        +-org.codehaus.plexus:plexus-utils:3.0.10
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.lib:lib-jenkins-maven-embedder:3.11
      +-org.apache.maven:maven-artifact:3.1.0
        +-org.codehaus.plexus:plexus-utils:3.0.10
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.lib:lib-jenkins-maven-embedder:3.11
      +-org.apache.maven:maven-compat:3.1.0
        +-org.codehaus.plexus:plexus-utils:3.0.10
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.lib:lib-jenkins-maven-embedder:3.11
      +-org.apache.maven:maven-embedder:3.1.0
        +-org.codehaus.plexus:plexus-utils:3.0.10
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.lib:lib-jenkins-maven-embedder:3.11
      +-org.apache.maven:maven-aether-provider:3.1.0
        +-org.codehaus.plexus:plexus-utils:3.0.10
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.lib:lib-jenkins-maven-embedder:3.11
      +-org.apache.maven.wagon:wagon-provider-api:2.4
        +-org.codehaus.plexus:plexus-utils:3.0.8
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.lib:lib-jenkins-maven-embedder:3.11
      +-org.apache.maven:maven-core:3.1.0
        +-org.apache.maven:maven-model:3.1.0
          +-org.codehaus.plexus:plexus-utils:3.0.10
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.lib:lib-jenkins-maven-embedder:3.11
      +-org.apache.maven:maven-core:3.1.0
        +-org.apache.maven:maven-settings:3.1.0
          +-org.codehaus.plexus:plexus-utils:3.0.10
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.lib:lib-jenkins-maven-embedder:3.11
      +-org.apache.maven:maven-core:3.1.0
        +-org.apache.maven:maven-settings-builder:3.1.0
          +-org.codehaus.plexus:plexus-utils:3.0.10
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.lib:lib-jenkins-maven-embedder:3.11
      +-org.apache.maven:maven-core:3.1.0
        +-org.apache.maven:maven-repository-metadata:3.1.0
          +-org.codehaus.plexus:plexus-utils:3.0.10
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.lib:lib-jenkins-maven-embedder:3.11
      +-org.apache.maven:maven-core:3.1.0
        +-org.apache.maven:maven-model-builder:3.1.0
          +-org.codehaus.plexus:plexus-utils:3.0.10
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.lib:lib-jenkins-maven-embedder:3.11
      +-org.apache.maven:maven-core:3.1.0
        +-org.sonatype.plexus:plexus-sec-dispatcher:1.3
          +-org.codehaus.plexus:plexus-utils:1.5.5
, 
Require upper bound dependencies error for org.codehaus.plexus:plexus-classworlds:2.4 paths to dependency are:
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.eclipse.sisu:org.eclipse.sisu.plexus:0.1.0
      +-org.codehaus.plexus:plexus-classworlds:2.4
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.lib:lib-jenkins-maven-embedder:3.11
      +-org.apache.maven:maven-core:3.1.0
        +-org.codehaus.plexus:plexus-classworlds:2.4.2
and
+-org.jenkins-ci.plugins:leaptest-plugin:3.1.0
  +-org.jenkins-ci.main:jenkins-test-harness:2.13
    +-org.jenkins-ci.lib:lib-jenkins-maven-embedder:3.11
      +-org.apache.maven:maven-embedder:3.1.0
        +-org.codehaus.plexus:plexus-classworlds:2.4.2
]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 14.877 s
[INFO] Finished at: 2019-01-22T13:33:28+01:00
[INFO] Final Memory: 48M/620M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce (display-info) on project leaptest-plugin: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Process finished with exit code 1

"schIds" box is not visible which makes makes it harder to configure for JobDSL and Pipelines

make it visible

[3.1.0] Add "Flow" keyframes/output to console log in stead of incorrect statement

Current console ( Statement does not make sense as it indicate that we are waiting, but we actually have a schedule running ):

Schedule xxx_dk--xxx_dk--smoketest[e6683b12-2ddb-4b9b-853f-c4fa18908e3b] Launched Successfully!
The schedule status is already 'Executing' - wait a minute...
The schedule status is already 'Executing' - wait a minute...
The schedule status is already 'Executing' - wait a minute...
The schedule status is already 'Executing' - wait a minute...
The schedule status is already 'Executing' - wait a minute...
The schedule status is already 'Executing' - wait a minute...
The schedule status is already 'Executing' - wait a minute...
The schedule status is already 'Executing' - wait a minute...
|---------------------------------------------------------------
Schedule: xxx_dk--xxx_dk--smoketest[e6683b12-2ddb-4b9b-853f-c4fa18908e3b]

"wait a minute" is actually the configured delay and not a minute. That is too "noisy"..

Output from 3.0.0 - style: ( desired - could be an option)

Schedule xxx.dk smoketest - afviklermaskine - xxx.dk[e6683b12-2ddb-4b9b-853f-c4fa18908e3b] Launched Successfully!
RunId: '313a09d7-3980-4b7c-a104-920e702e748d' is not ready yet - wait a minute
RunId: '313a09d7-3980-4b7c-a104-920e702e748d' is ready to monitor
----------------------------------------------------------------------------------------
RunItem: TTS-543 NB søgeboks på xxx.dk forside | Status: Passed | Elapsed: 29.1261534
2018-11-19T12:59:04.0221219+00:00 - Scheduled run executed from schedule 'xxx.dk smoketest - afviklermaskine - xxx.dk'
2018-11-19T12:59:04.0688448+00:00 - Connecting to Azure agent
2018-11-19T12:59:04.0688448+00:00 - Connected to Azure agent with size 1024x768
2018-11-19T12:59:04.240719+00:00 - Running
2018-11-19T12:59:04.871487+00:00 - Variable 'URL' was loaded with value 'xxx.dk'.
2018-11-19T12:59:09.320793+00:00 - Chrome was successfully started.
2018-11-19T12:59:17.7958832+00:00 - Chrome loaded url xxx.dk
2018-11-19T12:59:17.9208823+00:00 - Looping, current value is 1.
2018-11-19T12:59:31.171265+00:00 - Web element was not found within 10 seconds
2018-11-19T12:59:31.171265+00:00 - Breaking current iteration scope.
2018-11-19T12:59:31.1877461+00:00 - Loop is broken.
2018-11-19T12:59:31.7033066+00:00 - Left-clicked on web element 'A' at position 821:602
2018-11-19T12:59:31.9411172+00:00 - Left-clicked on web element 'DIV' at position 164:90
2018-11-19T12:59:32.2001211+00:00 - Found web element 'A' at position 194:397
2018-11-19T12:59:33.2013336+00:00 - Case is passed.
Environment: Azure agent

It helps debugging and comparing flow execution out from run to run.. In the current implementation it is not possible to see how a good run trace output. Only failures available in LeapWork. In LeapWork it is not possible to find runs by id's etc..
It helps understanding progress without opening LeapWork Studio

The default timeout is not visible for the user.. Move it to the UI as defaults

Extend the plugin to utilize variables on /api/v3/schedules/{scheduleId}/runNow extension point

Utilizing the option could enable usage of same schedule on different sites etc..

Using your example Pipeline script throws a "null/" error

Using:
Jenkins version: 2.154
Leapworks Intergration Plugin version: 3.0.0

We try to run UI test using your example:

  stage ('Leapwork Integration') {
    step([$class: "LeaptestJenkinsBridgeBuilder",
      leapworkHostname: "[LeapworksServer]",
      leapworkPort: "[LeapworksServerPort]",
      leapworkAccessKey: "[LeapworksServerAccessKey]",
      leapworkDelay: "35",
      leapworkDoneStatusAs: "Success", //"Failed"
      leapworkReport: "report.xml",
      leapworkSchIds: "[LeapworksScheduleID]",
      leapworkSchNames: "[LeapworksScheduleName]"
    ]);
    sh 'sleep 25s'
    step([$class: 'JUnitResultArchiver', testResults: 'report.xml']);

    if(currentBuild.result != "FAILURE") {
      echo "RESULT: ${currentBuild.result}  SUCCESS INFO"
      // do something else
    } else {
      echo "RESULT: ${currentBuild.result}  FAIL INFO"
      // do something else
    }
  }

The plugin starts with showing the path to report.xml:

[Pipeline] step
null/report.xml
//////////////////////////////////////////////////////////////////////////////////////
Schedule [LeapworksScheduleName][LeapworksScheduleID] Launched Successfully!
----------------------------------------------------------------------------------------
RunItem: JenkinsTesterCase | Status: Passed | Elapsed: 1.5080451
2018-12-10T14:01:32.0204739+00:00 - Scheduled run executed from schedule '[LeapworksScheduleName]'

--- SNIP ---

2018-12-10T14:01:33.5361637+00:00 - Case is passed.
Environment: [LeapworksScheduleEnvironment]
Schedule: [LeapworksScheduleName]
ERROR: Failed to create a report file!
ERROR: Leapwork for Jenkins plugin finished with errors!
ERROR: java.io.IOException: No such file or directory

Where does the null/ appear from?

Tried to use this as well:

leapworkReport: "${WORKSPACE}/report.xml",

The output is basically the same, save the output:

[Pipeline] step
null/[path/to/jenkins/job/workspace]/report.xml
//////////////////////////////////////////////////////////////////////////////////////

We did an ls -lrt and it shows a file called report.xml with size 0.

Plugin 'fails' when the connection to leaptest machine is not stable

I get the following error when the plugin throws an error while fetching a status from the leaptest machine.

Schedule: LeaptestSeleniumSchedule | Schedule Id: 9d04b802-a232-48b5-a17a-d54ca3afe5ee | Launched: SUCCESSFULLY

ERROR: Code: 500 Status: Internal Server Error!
ERROR: Tried to get LeaptestSeleniumSchedule[9d04b802-a232-48b5-a17a-d54ca3afe5ee] state! Check connection to your server and try again!
INVALID SCHEDULES:
9d04b802-a232-48b5-a17a-d54ca3afe5ee
Leaptest for Jenkins  plugin  successfully finished!

Emphasize in UI when schedules are "disabled", but still make it check-able for configuration

Current version the "checkbox" is disabled but
a) it is hard to see if all schedules are disabled and cannot be clicked
b) It is not possible to preconfigure Jenkins prior to enabling it in LeapWork.

No report is being generated

Hi,

I've created a jenkins job as described in https://leaptest.com/support/learning-center/jenkins-integration . The test runs fine but the report is not being generated.
The console output of the job looks like this:

Started by user Jakob Sack
Building remotely on xxx in workspace d:\workspace\xxx\Miscellaneous\Leaptest
Schedule: xxx | Schedule Id: 4e3ea8bd-745a-4f96-8c50-e65b5cc95cbd | Launched: SUCCESSFULLY
Case: AddQualification | Status: Passed | Elapsed: 00:01:09.2479432
ERROR: The system cannot find the path specified
Leaptest for Jenkins  plugin  successfully finished!
Build step 'Leaptest Integration' changed build result to SUCCESS
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
[BFA] Scanning build for known causes...
[BFA] No failure causes found
[BFA] Done. 0s
Finished: FAILURE

I'm using Leaptest plugin 1.1.0 with Jenkins 2.56 on Windows 7.

Have the plugin be able to be downloaded via the Jenkins plugin installer

It would be great to if this plugin could be able to be downloaded via the default Jenkins plugin installer. This would remove manual maintenance work in keeping our Jenkins instances up to date.

The plugin only works when running on master - fails to save report

Schedule <schedule name> [<shedule_id>] is still running!
----------------------------------------------------------------------------------------
Case: <test-case> | Status: Passed | Elapsed: 00:01:05.0066662
ERROR: Failed to create a report file!
ERROR: Leaptest for Jenkins plugin finished with errors!
ERROR: java.io.IOException: The system cannot find the path specified
ERROR: If nothing helps, please contact support https://leaptest.com/support and provide the next information:
1.Plugin Logs
2.Leaptest and plugin version
3.Controller logs from the moment you've run the plugin.
4.Assets without videos if possible.
You can find them {Path to Leaptest}/LEAPTEST/Assets
Thank you
ERROR: FAILURE
Build step 'Leaptest Integration' changed build result to FAILURE

The plugin uses File in stead of FilePath

[3.1.0] Plugin fails on failed test cases even configured with success

Done Status As: Success
Write keyframes of passed flows: false
Schedule xclsc1702[7c6f8dd2-5b24-4e7b-836e-0b4ae73c3958] successfully detected!
//////////////////////////////////////////////////////////////////////////////////////
Schedule xclsc1702[7c6f8dd2-5b24-4e7b-836e-0b4ae73c3958] Launched Successfully!
The schedule status is already 'Executing' - wait a minute...
----------------------------------------------------------------------------------------
........
Schedule: xclsc1702[7c6f8dd2-5b24-4e7b-836e-0b4ae73c3958]
Passed testcases: 0
Failed testcases: 1
Error testcases: 0
|---------------------------------------------------------------
| Total passed testcases: 0
| Total failed testcases: 1
| Total error testcases: 0
Creating report file by path: reports.xml
FAILURE
Leapwork for Jenkins  plugin  successfully finished!

This is really "crucial" for our pipeline that "flow" failures are treated as non-intrusive to the build execution

           pluginHandler.createJUnitReport(run,workspace,getLeapworkReport(),listener,buildResult);

            if (buildResult.getErrors() > 0 ) {
                listener.getLogger().println("[ERROR] There were detected case(s) with status 'Error', 'Inconclusive', 'Timeout' or 'Cancelled'. Please check the report or console output for details. Set the build status to FAILURE as the results of the cases are not deterministic..");
                run.setResult(Result.FAILURE);
                listener.getLogger().println("");
            }
            if ( buildResult.getFailedTests() > 0 ) {
                if ( "Success".equals(this.leapworkDoneStatusAs) ){
                    listener.getLogger().println("There were test cases that had failures/issues, but the plugin has been configured to return: 'Success' in this case");
                    run.setResult(Result.SUCCESS);
                } else if ( "Unstable".equals(this.leapworkDoneStatusAs) ) {
                    listener.getLogger().println("There were test cases that had failures/issues, but the plugin has been configured to return: 'Unstable' in this case");
                    run.setResult(Result.UNSTABLE);
                }
            } else {
                listener.getLogger().println("No issues detected");
            }
            listener.getLogger().println(Messages.PLUGIN_SUCCESSFUL_FINISH);

	String[] splittedKeyAndValue = rawKeyValuePair.split(variableSeparatorRegex);
	if(splittedKeyAndValue.length < 2){
	listener.getLogger().println(String.format(Messages.INVALID_SCHEDULE_VARIABLE,rawKeyValuePair));
	continue;
	}
	String key = splittedKeyAndValue[0];
	String value = splittedKeyAndValue[1];