Skip to content

Workflows

Artem Fedorov edited this page Nov 28, 2017 · 10 revisions

Run Test

This flow you can see in CiBuild.java. This Class takes the following parameters:

  • test - the test, that will be start on the BlazeMeter;
  • properties - properties, that will be send to the test. Properties must be a comma-separated string of key=value pairs, for example: username=USER_ADMIN,password=ADMIN_PASS;
  • notes - notes, that will be add to report;
  • isDownloadJtl - select this option for download JTL report;
  • isDownloadJUnit - select this option for download JUnit report;
  • junitPath - path in which will be saved JUnit report;
  • jtlPath - path in which will be saved JUnit report;
  • workspaceDir - parent path to junitPath and jtlPath.

This flow use the following algorithm:

  1. Start your test;
  2. Post Notes to Master;
  3. Post Properties to Master;
  4. Waiting for finish Master:
    • Get Master Status and sleep for N seconds (By default N = 10sec. You can change it by set Java System property bzm.checkTimeout)
  5. Run CiPostProcess:
    • Validate CI Status;
    • Download JUnit report if it required by user;
    • Download JTL report if it required by user;
    • Download summary report.

Get list of test

This flow you can see in TestsListFlow.java. This method return list of test from all your account and workspaces. It use the following algorithm:

  1. Get all accounts;
  2. For each account get workspaces;
  3. For each workspace get all tests;
  4. For each workspace get all multi-tests.
Clone this wiki locally