QV Scalability Tools (QV10,QV11,QV12)

[Daniel_Larsson]

This package (referred to as QVScalabilityTools) contains a complete set of tools for easy creation, execution and analyzing of load/performance tests and regression tests.

QlikView documents to help analyze result and log files(This was previously included in this package):Scalability Results Analyzer

Older versions of the tool can be found here: Tool for easy creation of load/performance tests of QlikView (v.10 and 11)

Tools for Qlik Sense can be found here: Qlik Sense Scalability Tools

Note: Using windows built-in unzip functionality will not allow the .exe to launch unless unblocking zipped package first (properties -> unblock).

Note: Regarding Apache Log4j, reference CVE-2021-44228 (also referred to as Log4Shell), these set of tools are not directly vulnerable to the exploit, however JMeter, the tool required as a separate download, is. How to mitigate the vulnerability for JMeter has been documented here : https://community.qlik.com/t5/Knowledge/Qlik-Scalability-tools-and-log4j/ta-p/1872009 

Included parts are:

• Standalone application for creating a JMeter script
• Support files for launching the script by utilizing the JMeter engine (JMeter installed is a pre-requisite)
• Documentation on how to use the package

Version 1.2.7->1.2.8

• Changes Section Access requests

Changelog 1.2.6->1.2.7

• NTLM support removed due current solution broken and lack of a new secure solution.
• Small updates for static content, for future product releases.

2019-08-26

Documentation updates due to:
- New recommended JMeter version (4.0)
- Changes to the licensing for the Oracle Java implementation (seehttps://www.oracle.com/technetwork/java/javase/overview/oracle-jdk-faqs.html)
- Open-source Java Development Kits (JDKs) have been verified for use with JMeter and the QlikView Scalability Tools

Changelog 1.2.5->1.2.6

• Added support for QlikView 12.50 and 12.20SR10

Changelog 1.2.4->1.2.5

• Added support for QlikView 12.30

Changelog 1.2.3->1.2.4

• Added support for JMeter 4.0 and Java 9.
• Bugfixes for regression testing
• Added actions: Select Excluded, Select All, Select Possible
• Added support for 12.20 SR3

Changelog 1.2.2->1.2.3

• Bugfix for export to excel action
• Added transfer state (bookmark) support for document chaining
• GUI: Template selection more accurately show supported Qv versions

Changelog 1.2.1->1.2.2

• Bugfixes, make sure minimum amount of selections are respected in certain corner cases

Changelog 1.2->1.2.1

• Improved performance for high throughput scenarios

Changelog 1.1 -> 1.2

• Improved assertions logic to show faulty actions as errors
• Change JMeter template scripts to use groovy instead of beanshell
• New prerequisites:
  • JMeter version 3.0
  • Java 64-bit JRE 8

Your use of QVScalabilityTools will be subject to the same license agreement between you and QlikTech for QlikView Server. QlikTech does not provide maintenance and support services for QVScalabilityTools, however please check QlikCommunity for additional information on use of these products.

PLEASE NOTE:

The supported versions of Java are 8 and 9. Supported version of JMeter are 3.0 and 4.0, but not 3.2

[andrewmcgough]

I am experiencing the same issue. The following Evenit is logged "Restart: Server aborted trying to recover by restart. Reason for restart: Phoenix detected: Performance monitor stuck"

[korsikov]

Help me plz.

I can't run QV scalability tools regresion test. Have error Java.exe not found, please make sure java is installed...

But jmeter.bat start normaly. And PATH set in correct

C:\Users\korsikov.RBCGRP>java -version

java version "1.8.0_25"

Java(TM) SE Runtime Environment (build 1.8.0_25-b18)

Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)

C:\Users\korsikov.RBCGRP>

[Sebastian_Fredenberg]

Hi Alexander,

Is this this an issue?

If so, does the error occur when you try to start the scalability tools gui or does it occur when you try the regression test capabilities?

It is strange, as if you can start jmeter.bat then the scalability tools should launch just fine, and there should not be any difference with the regression parts.

You could always try and put the scalability tools in the same folder as jmeter, or run as administrator to rule out any issues with folder access.

/sebastian

[korsikov]

move QV Scalability tools folder to c:\jmeter and can run test.  Now the task is running. Waiting for results. It's better than nothing.

[#6]

Hi everybody,

This is the first time I tried QV Scalability Tools. I just read the QVScalabilityTools.pdf in the folder.

At first step we created the test scenario but I've got a problem with the scenario tab.

I selected folder and I've got a message : "There was a problem reading the file. Please verify permissions and try again."

Does anyone could help me ?

Regards,

Marine

[Sebastian_Fredenberg]

Hi Marine,

Do you get that error message when selecting the project files folder? If so, make sure that the project files have been exported properly (you should a bunch of xml-files in it). Also you can try and move that folder in in case there is an access issue to the current folder it resides in.

cheers

/Sebastian

[jerrysvensson]

Hi

I have a problem with applications that has Section access. Apps without SA works fine.

Tried adding :userid=user&password=pwd to the Document URL. Which works if I try it in IE.

There is a Section entry in the Script generator (..\SupportFiles\sectionaccess.txt). Should I create that file and add a user? Format?

I am looking into Regression testing,

[jerrysvensson]

Never mind, found the manual...

[jerrysvensson]

Hi

Found a problem with Object IDs containing _, like MB_Selection. In the Regressions result file it says MB. We use _ in almost all objects.. Any workaround/setting I missed?

[PawelF]

Hi Jerry,

Thank you for pointing this out. One of our team members was able to reproduce this behavior.

I did have a closer look at this functionality. For some variables JMeter automatically creates additional ones which using underscores, which is most probably the reason why it does not work in your case.

We will look into this, and check what can be done. When we have more information, I will post it here.

If we manage to solve the issue, the fix will be included in next version of the tool.

Pawel