Check Out the Latest News About SmartBear Connect
New Idea

Dear all,


I am unable to record scenario for media streaming. Please assist me


For more information download the video :


As suggest by Alexey Kryuchkov  submit a feature request to the following Community.

I am missing a feature to easily enable/disable created lines in validations / data extractor modules.

By creating a feature that easily enable/disables them (using checkboxes) it's easier to work with LC.

See attached screenshot for illustration.

0 Kudos

There is currently lacking a horizontal graph bar in the Custom Graph section - therefore not possible to view the last part of the graph - Please include a horizontal scroll bar in this screen.



Implement validation based on numeric value

Status: New Idea
by on ‎05-22-2017 08:02 AM

This feature request is based on following:

I need to implement a validation, based on value of ContentLength. The test should fail if ContentLength equals 0.

I have read the info about validation here. But this only works for validation on strings.


I want to have a validation based on numeric value of a response. Of course, the value of the Contenlength changes for every request (it's not a fixed value). Only thing that counts is that validation should pass if ContentLength value > 0, and that it should fail in all other cases.


There is currently no easy way to implement such validation. I would like LoadComplete to be improved with such easy validation. See attached screenshot for clarification.



0 Kudos

I would like to ask for the possibility to concatenate the values of two variables into the third one. This can be implemented in the same tables where data are extracted from the responses and assigned to the variables (Data Selectors, etc.).

In this case, the value of the 'Source' field (using Data Selector table as an example) may be 'Variables', 'Regular Expression' will specify the name of the first variable (e.g. @Var1), 'Subexpression' will specify the name of the second variable (e.g. @Var2) and the 'Save to Variable' field will specify the name of the variable that contains concatenation result (e.g. Var3).

It would be perfect, if it is possible for Var1 and Var2 specify not only variable name, but some string that contains (or not) the variable - e.g.: if Var1 = 'CaseId' and Var2 = '123', then '@Var1' and '=@Var2' should concatenate to 'CaseId=123'.


Please let me know if you need more details for this request.

Status: Implemented
0 Kudos

Perform Load test on SAP

Status: New Idea
by Daoulas on ‎09-18-2015 03:04 AM

Perform Load test on SAP , which is a client application and does not run from a web browser.

0 Kudos

In order to be able to create more real-life test scenarios I would like to ask to make it possible to use variables as operation parameters.
For example, a sample scenario is to make a user to order a random number of items.
The idea of how to implement this is to record the ordering of one item, add the Loop operation to the scenario and move relevant requests into the loop.
The current problem is that the loop can repeat only the fixed number of iterations.
Expected improvement is that it will be possible to create a project variable of random type in the range, say, from 1 to 10 and reference this variable as a loop counter.
The expected result is that every virtual user will order random number of items in the range between 1 and 10.


Currently, this window is fixed in size. Meaning you have to scroll left and right to view/edit the found parameters.

Could be easier if this popup window could be maximed / made bigger.





Initial clauses:
Consider this use case as a sample: login - get one page with items list - order one item - purchase ordered item - logout. The root idea is that because of reusability and maintenance considerations, it is better to record and execute not a lot of similar complex end-to-end scenarios, but several smaller separate stand-alone ones and combine them using the Call Scenario operation.
It is expected, that using this approach it will be possible to create, for example, these additional scenarios:
-- login - logout;
-- login - get random number of pages with items list - logout;
-- login - order random number of items - purchase items - logout.
From the reusability point of view it is expected that if, for example, the login scenario changes, only this simple scenario has to be recorded and correlated a-new but not all affected large and complex scenarios. It should be noted here that while it is possible to refresh the correlation rules for the already existing scenario, this does not apply to scenarios launched from the Call Scenario operation.

The above considerations are, probably, the major cornerstone for my feature request, so please let me know if my initial idea is wrong, not recommended or is not adopted by real practitioners because of some reason.

If the above idea is an acceptable one, it is obvious that data correlation will be required when combining separate scenarios to work together. I believe that this can be done more or less easily with the existing functionality of LoadComplete when complete scenario is recorded initially and is split later to several smaller stand-alone ones.

Now the problem:
Assume that in the course of the project, the page that displays items list (Items List page) was modified and requires different set of requests to be displayed. This means that the scenario that obtains this page must be re-recorded and correlated with the existing scenarios.
In its turn this means that (some) of the Data Selectors and Data Replacers that existed in the initial version of the Items List page must be recreated for the updated version of the page.

Actual request:
In order to make it more easy and convenient to find Data Selectors and Data Replacers in the initial version of the page, create them (only the needed ones, probably, with some modifications) in the new version of the page and apply at proper places, some functionality for side-by-side comparison of the requests that belong to two different pages with the possibility to modify requests of the target page should be useful and helpful.
Could you please consider this?

Thank you for your consideration.


P.S. This feature request is based on the Case #00222701 and might be related to the thread.


support renaming scenario's in Call To

Status: New Idea
by on ‎06-07-2017 05:32 AM

Currently (version 4.6), when you rename an already created scenario, the new name is not automatically inherited.

Resulting in errors, just because you rename a scenario.


Please support renaming scenarios as it should be.



0 Kudos

This would allow the test to be edited with any common mass update facilities, without having to include them in LC.

The import facility could then perform a validation to ensure that the test was compatible with the proprietary rules in LC and the tests could be used in their updated states.


The validation routine could then add stamps to indicate:

1. It has been edited with ... <tool name>, date time stamp and reference the original test.

2. A Label to allow brief notes on what was done

3. A flag to indicate it has been externally edited, 


Not all required, but these would help in mixed test environments.


Alternatively: Make tests editable with other editors directly (probably more difficult, and with less control of content).

0 Kudos

When editing a tests requests, allow the users to set up the screens as they need them for that session or user, and have a lock button so that for each request, the work area remains in the same configuration, so that they don't need to keep changing things around  each time.


A found in one session where I had to check every request I sent 20% of the time changing the environment around.

0 Kudos

When setting up a run of tests allow the user to apply a filter to the output to the log file allowing them to filter on

1. Duration

2. OK/Warning/Error

3. Ranges of Request ID/ Time period/ Call Types/ Machine/ Test/ and so forth


This will reduce unwanted data, allow tests to be for longer before exceeding log file size limitations.

In addition, when the data is exported, the data will be ready for processing and require less time to use.

0 Kudos

Currently the emulated connection speed, is not displayed anywhere in the report.

Please include this in the General Info section.




Currently, when you disable the option to launch a specific browser, you cannot select option "record traffic from this browser only" . (it's only enabled if you enable the launch option).


Consider this scenario: I don't want LC to start a browser, however I only want to record data from browser Chrome.


In current setup, this is not possible. So, I want LC to be updated to support this scenario.



0 Kudos



Please guide me if I missed this functionality in LoadComplete, but I think that variables created using the Variables panel are lacking some dynamics.

For example, I often need the random date that is not in the future but may be equal to today. The current implementation of Variables makes it possible to generate a random date variable, but only within hardcoded dates range.

I think that it might help if it is possible to implement some set of simple macros in LoadComplete so that, for my example, it is possible to specify, say, {CurrentDate} in the To field of the Variable Wizard and get a random date value from some date in the past and up to today.



Report comparison handling

Status: Implemented
by Staff on ‎03-13-2015 01:09 PM

In the Compare Results interface, it would be nice if users could easily specify which report will be Report A and which will be Report B. As it stands, whichever report is selected first becomes Report A, and it's confusing to figure out how to rearrange test results.

Status: Implemented

Implemented in LoadComplete 3.2

0 Kudos

Make Global Variables to be of table type

Status: New Idea
by Community Hero AlexKaras ‎01-29-2016 01:03 AM - edited ‎01-29-2016 01:06 AM



Problem: Now the global variables (those used for parameterization and accessible via Variables editor) that retrieve values from the databases, CSV-files, Excel files can be associated with a single field only. This is very inconvenient if, for example, variables must contain correlated values like user id and the password.


Request: Make the global variables to be of table type so that they can be associated with the resultsets. Access to the columns can be made using the 'dotted' notation. If resultset contains only one field, the old syntax can be used.


Use case sample: The LTLogins variable can be associated with the 'Select Login, Pwd From Logins Where Active=true;' resultset and provide data to some web site login form using the @LTLogins.Login and @LTLogins.Pwd syntax for the Login and Password fields accordingly.



Adjust scales in Custom Charts

Status: Implemented
by Staff on ‎08-19-2015 07:22 AM

For some metrics like %CPU and %Disk Time, the scales created in Custom Charts do not make intuitive sense. In the below example, the scale for %CPU goes from 0 - 600. This makes it harder to visually interpret the chart.


Would be nice to fix this for metrics that are percentage values, or perhaps give the user the ability to manually adjust the scales. (This could also be useful to create a unified report in some fringe use cases of running multiple simultaneous load tests against the same server.)



Status: Implemented

Implemented in LoadComplete 3.2