QF-Test

v2.1.1

  • An exception could occur when adding/modifiy a QF-Test job in the Jenkins jobs configuration..

Installation options

v2.1

  • Additional and more advanced concepts of the jenkins pipeline mode are now supported:
    • The QF-Test step can be run in a customized environment, which can e.g. be defined by means of the environment statement in a pipeline script. All relevant configuration parameters undergo parameter expansion with respect to the environment set. (By contrast, groovy variables are inherently handled by the interpreter. Their substitution is unaffected by this.)
    • The QF-Test step returns now an info object of type QFTestInfo. At the moment, it solely encodes the Jenkins build result that has been assigned to the QF-Test step (QFTestInfo::getJeninsResult())
    • The aforementioned build result is additionally attached to the flowNode representation of the build step. A Jenkins blog post disscusses the concept in greater detail.
  • The Console Log has been reworked, informing now about overwritten command line parameters. It also reports missing testsuites and steps without any referenced testsuite.
  • Extra command line parameters concerning the report generation can be specified.
  • The path to the QF-Test installation directory can be set again to point to a specific QF-Test version. This eliminates the breaking change introduced in v2.0. Both options are possible now. On windows nodes, a binary path pointing to a qftest.exe program will be silently replaced by its qftestc.exe counterpart, if both executables exist in the same directory.

Installation options
  • don't rename report.html (otherwise internal linkage was broken) - Thanks to @markusmo3
  • Do not override defined parameters with default settings
  • correct expansion of environment variables

Installation options
Installation options
  • Resetting returnValue before starting a new test run
  • Reenable junit report generation

Installation options
Installation options
Installation options
Installation options
Installation options

The whole plugin was re-implemented to support jenkins classic mode and pipeline mode as well.

  • Full support of Jenkins pipeline mode
  • The QF-Test influence on the general Jenkins build result is know configurable
  • Consistency fixes when handling multiple independent suite name / parameter pairs
  • No post steps invocations are required any more. The entire functionality is now provided by the plugin itself:
    • QF-Test execution including report creation
    • Publishing of run logs and the test report on the Jenkins build result page
    • Setting the Jenkins build result
  • Breaking change: The default location of the QF-Test log directory changed. (This will also break legacy configurations with the now obsolete post build steps relaying on explicit log path)
  • Breaking change: Direct support for QF-Test runs in daemon mode has been dropped. It can still be configured via the customParam option. In an Jenkins build environment we recommend the usage of Jenkins agents instead.

Installation options
Installation options
Installation options
Installation options
Installation options
Installation options
Installation options
Installation options
Installation options