When there are multiple databanks configured and one of those databanks is replaced, all the data mapping gets wiped off from the script. This causes rework. It would be great if we have to update mapping for only the file which was updated and not redo mapping of already configured databanks all over again.
... View more
Status:
New Idea
Submitted on
01-09-2019
12:39 PM
Submitted by
MichaelPunsky
on
01-09-2019
12:39 PM
I am referring to logic operators that will enhance LoadNinja Scenarios:
Conditional Loop
Call Scenario (in order to create compound scenarios)
IF-THEN-ELSE
While
Rendezvous Point
... View more
Status:
New Idea
Submitted on
01-10-2019
01:58 PM
Submitted by
MichaelPunsky
on
01-10-2019
01:58 PM
Since the majority of users hitting a web page are mobile users, adding support for mobile testing is necessary. Of course, there are various levels of mobile testing support - and actually different types of support. I would think that just having the ability to change the browser string so that the load appears to be coming from a mobile device, and maybe having a few bandwidth selections to simulate mobile traffic might be eough initially.
... View more
Status:
Implemented
Submitted on
01-17-2019
05:57 AM
Submitted by
MichaelPunsky
on
01-17-2019
05:57 AM
Use Case: Often a tester will want to have multiple scripts that only differ in a few aspects. It would be great if a script could be cloned within the project - With the new copy having a different name. That script could then be edited to reflect the differences.
... View more
Status:
New Idea
Submitted on
01-11-2019
01:20 PM
Submitted by
MichaelPunsky
on
01-11-2019
01:20 PM
Default thinktime should be set to "Minimum" as opposed to "Recorded". Screen CAP attached
... View more
Status:
New Idea
Submitted on
01-11-2019
01:03 PM
Submitted by
MichaelPunsky
on
01-11-2019
01:03 PM
SoapUI/LoadUI
TestComplete
AlertSite
... View more
Status:
New Idea
Submitted on
01-11-2019
01:01 PM
Submitted by
MichaelPunsky
on
01-11-2019
01:01 PM
self-explanatory
... View more
Dear colleagues,
I am pretty sure that compaund Web Test is in your plans for the next LoadNinja update.
The purpose of compaund Web Test is similair to the Call Scenario operation from LoadComplete and its purpose to make it possible to create reusable parts of Web Test.
For example, assume that I need to load test a scenario when 80% of VUs just browse some goods catalogue and only 20% of all VUs do a purchase.
Current implementation of LoadNinja requires that the browse sequence must be recorded (and supported) twice - for browse test and for browse and purchase one.
Compaund Web Test should eliminate this duplication.
... View more
Status:
New Idea
Submitted on
01-31-2019
07:49 AM
Submitted by
MichaelPunsky
on
01-31-2019
07:49 AM
DISTRO: Option 1: Databank(s) is automatically split into the same number of files as the number of load generators. Each load generator gets its own fraction of the original file. This is the most common use case. A row of data is UNIQUE across all load generators.
Option 2: The Databank(s) is sent in it's entirety to each load generator. A row of data is only UNIQUE for a load generator - not across all load generators.
END OF FILE BEHAVOR:
Option 1: Upon reaching the end of the databank, start again from the beginning of the file.
Option 2: Upon reaching the end of the databank, stop the test.
DATABANK ACCESS:
Option 1: Sequential
Option 2: Random
... View more
Status:
New Idea
Submitted on
01-29-2019
05:33 AM
Submitted by
MichaelPunsky
on
01-29-2019
05:33 AM
Provide the ability:
to see all hosts captured as part of the recording
to select which 3rd-party hosts are used (uncheck host to filter it out, check to re-activate)
Add:
List of Active hosts to the SUMMARY tab in the realtime report
List of Inactive hosts to the SUMMARY tab in the realtime report
List of Active hosts to the actual report
List of Inactive hosts to the actual report
... View more
Status:
New Idea
Submitted on
01-17-2019
06:09 AM
Submitted by
MichaelPunsky
on
01-17-2019
06:09 AM
Actually, I think various types of items should be color coded to stand out. Keyboard Input items should stand out because they will often be edited in some way.
For example:
Today, I recorded a script and while recording, took a couple of missteps. I had a typo in the password field and had to backspace and retype (twice!). It was easy to go in and edit the initial password to be perfect and then delete the other two password-related items. What took the longest, was LOCATING the keyboard items 😉 They are not hidden, but do not stand out.
... View more
Status:
New Idea
Submitted on
01-11-2019
12:48 PM
Submitted by
MichaelPunsky
on
01-11-2019
12:48 PM
This is an idea that I have heard many times over the years. Think how easy it would be to run a meaningful test that is based on actual useage patterns!
... View more
Status:
New Idea
Submitted on
01-09-2019
12:44 PM
Submitted by
MichaelPunsky
on
01-09-2019
12:44 PM
Enable validations around the concept of SLA's.
Example:
In a scenario, you select that Steps can not average greater than 3 seconds response time and no step can have a response time > than 5 seconds.
If exceeded, an SLA violation error is thrown and the script continues.
Reports should have an SLA section that highlights compliance with the selected SLA.
... View more
Status:
New Idea
Submitted on
01-09-2019
12:32 PM
Submitted by
MichaelPunsky
on
01-09-2019
12:32 PM
The ability to select, and combine cloud regions is essential.
Example: US-based Retailer wants to run a test representing their customer base. 50 percent could be generated in US-EAST and 50 percent US-WEST.
Example: Australian company wants to run tests. The load should be generated from AUS as anything else will add unrealistic latency.
... View more
Dear colleagues,
Could you please consider and unify the meaning of Test and Scenario for LoadNinja and LoadComplete?
At present they have opposite meaning and this may confuse the one who uses both tools.
... View more
Some values are generated during runtime, like OrderID, CartKey. Should have ability to extract these values from HTML / JSON response for UI and API scripts and store it in a file
... View more
There is no way to check the raw requests that are being sent in case we want to verify the requests on failed runs.
... View more
Having variables like in API script would help parameterize URLs and switch between environments easier.
... View more
Should have an ability to generate random unique values at runtime or append a random value to a variable like "TestUser_<random number / timestamp>", for scenarios such as username in signup functionality.
... View more