Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Karate tests pipeline

This is a job to launch karate tests against existing environment -

Job parameters:

  • branch - karate tests repository branch to checkout
  • modules - comma separated list of modules to build(no spaces). Karate tests is a multimodule Maven project, using this parameter you can specify exact maven modules to be build. If no value is provided than all the modules will be built.
  • threadCount - number of parallel thread to build. Uses maven parallel build capabilities ( Note: karate tests also can use multithreading inside.
  • okapiUrl - target environment OKAPI URL
  • tenant - tenant name for tests
  • adminUserName - admin user name of the ${tenant}. This user will be used to create a new tenant for each test, so it must have appropriate permissions
  • adminPassword - admin user password
  • prototypeTenant - a name of the tenant which will be used by karate tests as a prototype during new tests tenant creation. Specifically to determine versions of the modules which should be activated for test tenant

Job steps:

  1. Checkout karate tests repository
  2. Build karate config - prepare "karate-config-jenkins.js" which is used to provide parameters(url, tenant, user, some secrets) to karate tests
  3. Run karate tests - execute maven build
  4. Publish tests execution results - publish cucumber and junit reports
  5. Archive artifacts - executed only if job has been triggered by another job - archive karate, cucumber and junit tests result files

Scheduled karate tests pipeline

This is a job which creates a new environment, launch karate tests against it, drops environment, sends tests results notifications and creates Jira tickets -

This is job is designed to be triggered by cron.

Job parameters:

Scheduled run parameters values:

  • branch - master
  • threadCount - 4

Job steps:

  1. Create environment - execute to create a new "karate" environment on "folio-testing" cluster. Folio configuration is taken from "platform-complete" repo, "snapshot" branch.
  2. Run karate tests - execute against environment created on previous step
  3. Destroy environment - execute to destroy "karate" environment on "folio-testing" cluster
  4. Copy downstream job artifacts - copy karate tests execution results to current workspace
  5. Publish tests execution results - publish cucumber and junit reports
  6. Collect execution results - iterate over "karate-summary-json.txt"(generated by karate framework) to collect data regarding specific tests execution details. Then iterate over all cucumber htmls generated for test execution to match data from "karate-summary-json.txt" with a specific test report html file.
  7. Parse team assignment - parse data regarding module-team assignment from "teams-assignment.json" file.
  8. Send slack notifications - send slack notifications regarding failed tests to team channels
  9. Sync Jira tickets - synchronize failed karate tests Jira tickets - create/update/close karate tests Jira tickets according to tests results.

Karate Jira tickets flow

All tickets are created in "AQA" Jira project with "Bug" type and "P2" priority. Also all tickets have "karateRegressionPipeline" label. If team is specified for a karate test module in "team-assignment.json" file then appropriate team name will be set to "Development Team" field.

Image Added