Version 6.1.5

This is a companion discussion topic for the original entry at

The plugin “Report Basic”, isn’t works with command line execution, after this execution that reports(.xml, .html, .pdf, etc…) isn’t generate on project folder of test suite execution.


Thank you for your feedback. Please check if the API key was present in the command line.

It’s Working, thank You!!

1 Like

@ devalex88,

I hope KTS have some documentation on this .

How can I use this new capability?

  • Added the capability to use variables in XPaths when finding test objects.

First, you need to create an object using variable in its xpath:

Next, you call this object and pass value for the object variable from a test case:

postman plugin import creates an empty Postman folder.

It appears that with KS docker image version 6.1.5 there is some issue with generating reports when executing from Jenkins (or at least with uploading reports)… everything works with 6.1.4

Post stage
[Pipeline] junit
Recording test results
No test report files were found. Configuration error?
Error when executing always post condition:
hudson.AbortException: No test report files were found. Configuration error?
at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(
at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(
at hudson.FilePath$
at hudson.remoting.UserRequest.perform(
at hudson.remoting.UserRequest.perform(
at hudson.remoting.Request$
at hudson.remoting.InterceptingExecutorService$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$
at hudson.remoting.Engine$1.lambda$newThread$0(
Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from ip-10-255-0-5.ec2.internal/
at hudson.remoting.Channel.attachCallSiteStackTrace(
at hudson.remoting.UserRequest$ExceptionResponse.retrieve(
at hudson.FilePath.act(
at hudson.FilePath.act(
at hudson.tasks.junit.JUnitParser.parseResult(
at hudson.tasks.junit.JUnitResultArchiver.parse(
at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(
at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(
at java.util.concurrent.Executors$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$
… 1 more

[Pipeline] }

Hi. But this feature is already implemented in the older versions as well…why it is mentioned for this 6.1.5 RN? Thanks.

@Rasko_Pjesivac Please see this tutorial

Before 6.1.5 it was available for Attributes mode only.

What has happened to Web Record?

but this feature has been added like a century ago, what’s new about it?, we also have official documentation for this, so did I miss something important here on this new feature?

Web recorder is still here.

Will this version will resolve the issue of lastest chrome driver compatibility issues

Import from Postman does not work.
I can see Postman folder only.

Well this xpath with variables, never has worked for me, not even in this last release…

It supposed to locate this hyperlink

You should select the checkbox “select the object by” in order to use this, if you want to store multiple xpath in 1 Test object, you might have to alter your code a little bit