Skip to content
UmapathiM001 edited this page Nov 11, 2022 · 1 revision

Tabjolt supports several custom parameters which are passed to the test class which uses it to execute the test with requirements based on the param values. Custom parameters are passed through the command line using the --z or --customParams switch. Custom parameters are used with specific jmx files eg:InteractVizLoadTest.jmx and Replay.jmx.

With InteractVizLoadTest.jmx Tabjolt will execute parallel tests based on the thread count to perform login, GET request to URL, bootstrap(to load the view), perform interactions etc. To provide more flexibility to test various scenarios during viz load the custom params can be used to change the default. e.g. _RunTabjolt.bat --t=testplans\InteractVizLoadTest.jmx --z={interactWeight:0.5,vizPoolFile:Vizpool.csv,skipCacheRatio:0.4} _ The value of the --z or --customParams switch is specified in Json style - surrounded by curly braces, delimited by commas, name and value separated by colon.

  • Parameter: interactWeight
  • Used to specify the probability an interaction with the loaded viz is executed. 0 means interaction is never executed, 1 means interaction is always executed, 0.5 means half of the interactions are executed.
  • Parameter: skipCacheRatio
  • Used to specify the probability caches are skipped during viz load. 0 means cache is never skipped, 1 means cache is always skipped, 0.5 means cache is skipped half of the time.
  • Parameter: forceLogin
  • o Used to require login to the server before viz load. Supported values - true or false.
  • Parameter: vizPoolFile
  • o Used to override the pool of vizzes to load. File must exist in config folder of Tabjolt.
  • Parameter: userPoolFile
  • o Used to override the pool of users to use for login. File must exist in config folder of Tabjolt.

The parameters interactWeight and skipCacheRatio are particularly useful to make test execution more realistic workload pattern. If customers determine that users interact on the vizzes only 50% of the time then the simulation should use interactWeight:0.5, if the goal is to test only loading the viz and no interactions then interactWeight:0 should be used. Skipping the cache hits is necessary to make the workload realistic, if customers user small set of URLs(viz links from vizpool.csv) then after the initial load of vizzes rest of the responses will be very fast as results will come from various caches. To make it more realistic skipCacheRatio should be used, the recommendation is to use 0.3 to 0.5 to skip 30- 50% of the caches and let the viz load do full bootstrap.

Replayer-specific Custom Parameters

These parameters go with a Replayer test execution, e.g. RunTabjolt.bat --t=testplans\Replay.jmx --z={replayFile:Replay_PublicVizpool3.json,loadMultiplier:1,refreshCache:no,disableSharedSessionsCache:no,skipAuth:yes}

  • Parameter: replayFile
  • The Json file with sessions for the tool to replay.
    
  • Parameter: loadMultiplier
  • Multiply the load specified in the Json file by the specified value.
  • Parameter: refreshCache
  • Specify whether cache should be refreshed during load replay. Supported values - yes or no.
  • Parameter: disableSharedSessionsCache
  • Specify whether session cache should be disabled during load replay. Supported values - yes or no.
Clone this wiki locally