details.title details.private

administrators

details.members

  • RE: JMeter vs ReadyAPI SOAP API Performance Testing

    Not only the server need to be able to respond fast enough, JMeter must be able to send requests fast enough as well.

    Default JMeter configuration is suitable for tests development and debugging and creating some load (rather limited though), you need to properly tune your JMeter instance in order to fully utilize your machine resources
    If your single machine is not powerful enough to conduct the required load it's possible to run JMeter in distributed mode using as many load generators as needed in order to create the necessary number of virtual users/requests per second

    global:posted_in, Performance, Load, Stress Testing
  • JMeter vs ReadyAPI SOAP API Performance Testing

    Scenario: Read data from a CSV file with unknown number of records. Use the data to create Soap XML MSg and Post Method. Continue to do this until all the records have been read.

    Problem: I used ReadyAPI to perform these actions and was able to achieve the intended TPS at server with whatever i have provided in VU's option. Tried with 150 vu's and observed constant load of 150 requests at the server. But when i try to do the same in JMeter, i was not able to achieve more than 70 TPS and the load isn't evenly distributed as well no matter how many threads i use. I am using a Thread Group, CSV DataSet Config, UserDefined Parameters to create unique request ID and JSR223 PreProcessor with Groovy Script as a child of HTTPRequest to remove empty xml tags.

    Read some posts where it was mentioned that JMeter throughput will be stagnant based on servers response capability. But it's not in my case since i can generate 150TPS with ReadyAPI. Annual Licensing costs and Renewal costs associated with ReadyAPI is the Reason that i am looking for solution with JMeter.

    global:posted_in, Performance, Load, Stress Testing
  • RE: Dynamic variable for a value from array in Postman
    let jsonData = pm.response.json(); 
    pm.environment.set("test_name", jsonData.test3[0].id3);
    

    test3 is an array so you have to get the first object and then id3

    global:posted_in, API Testing
  • Dynamic variable for a value from array in Postman

    Any ideas on how could I add an automatic environmental variable in Postman based on a value which is appearing in the endpoint response in the array? In the example below, I would like to use the "id3" value and save it as a dynamic variable.

    {
    "test": 123,
    "test2": [],
    "test3": [
            {
                "id": 0,
                "id2": 4554336,
                "id3": 30,
                "id4": 0
            }
        ]
    }
    

    I thought it will be simple as: let jsonData = pm.response.json(); pm.environment.set("test_name", jsonData.test3.id);

    but this set up is saving the variable with a null value.

    global:posted_in, API Testing
  • RE: Multiple SQL statements together?

    The where clause is redundant. You can just add all to a single query:

    select count(column1),
           count(column2),
           . . .
           count(column20)      
    from t
    
    global:posted_in, SQL, Database Testing
  • Multiple SQL statements together?

    I am testing each column in a table to see if it has null values. Currently, I am using:

    select count (column) when column is not null
    

    I have a list of 20 of these for each column. Can I combine them all to run it once and then tell me the record count for each column. Any column that has 0 would be a null column

    global:posted_in, SQL, Database Testing
  • RE: Jmeter doesn't show results when executed on slave, both GUI and CLI

    The .csv file in what the test are based must be in the slave inside the JMeter bin folder /bin/data/yourFile.csv

    global:posted_in, Performance, Load, Stress Testing
  • RE: Jmeter doesn't show results when executed on slave, both GUI and CLI

    How about slave log? Given the symptoms I can think of 3 possible reasons:

    • Your test relies on external data file, i.e. CSV file or .properties file, if this is the case - you need to copy all the dependent files to all the slave machines
    • Your test relies on a plugin which is not installed on the slave(s), either copy your JMeter installation from master to all the slaves or use JMeter Plugins Manager to install the missing plugins
    • Your RMI configuration is not correct, i.e. port which is used for communication from the slave to the master is random by default, you might want to set it explicitly and open it in firewall

    In order to be able to tell more I need to see your jmeter-server.log file (it's being generated in "bin" folder of your JMeter installation given you launch the slave process via jmeter-server.bat file, if you use other approach you can set the desired log file name/location via -j command-line argument

    global:posted_in, Performance, Load, Stress Testing
  • Jmeter doesn't show results when executed on slave, both GUI and CLI

    Introduction:
    I'm new to Jmeter, so I'm working with basic tasks but I have a mentor. We are working with distributed architecture, one master and one slave in my local network executing a real world working testplan.

    Problem:
    No response from slave:
    We have installed and configured Jmeter 5.3 and java version "1.8.0_271" in both slave and master with windows 10 machines. Each machine can ping the other. When the testplan is executed in the master, from the JMeter GUI or CLI, the slave recognize the order and start the proccess, it also notify the end, but there is no response in the .jtl file another than the file header. We have tryed with RMI enabled and disabled. The logs dont show errors.

    System specs: OS W10, Jmeter 5.3, Java 1.8, Jmeter plugin: jmeter-plugins-manager-1.4.jar (Plugins installed: Custom Thread Groups, 3 Basic Graphs, Console Status Logger), Windows Firewall is disabled in both machines, Jmeter properties (Master remote_hosts: Slave ip, Slave remote_hosts: 127.0.0.1)

    JMeter GUI execution log (Master):

    2020-12-11 11:33:45,446 INFO o.a.j.e.DistributedRunner: Configuring remote engine: 192.168.1.135 2020-12-11 11:33:45,446 INFO o.a.j.r.RmiUtils: Disabling SSL for RMI as server.rmi.ssl.disable is set to 'true' 2020-12-11 11:33:45,624 INFO o.a.j.e.DistributedRunner: Starting distributed test with remote engines: [192.168.1.135] @ Fri Dec 11 11:33:45 CET 2020 (1607682825623) 2020-12-11 11:33:45,624 INFO o.a.j.e.ClientJMeterEngine: running clientengine run method 2020-12-11 11:33:45,629 INFO o.a.j.r.RmiUtils: Disabling SSL for RMI as server.rmi.ssl.disable is set to 'true' 2020-12-11 11:33:45,629 INFO o.a.j.r.RmiUtils: Disabling SSL for RMI as server.rmi.ssl.disable is set to 'true' 2020-12-11 11:33:45,630 INFO o.a.j.s.BatchSampleSender: Using batching (client settings) for this run. Thresholds: num=100, time=60000 2020-12-11 11:33:45,630 INFO o.a.j.s.DataStrippingSampleSender: Using DataStrippingSampleSender for this run 2020-12-11 11:33:45,630 INFO o.a.j.r.RmiUtils: Disabling SSL for RMI as server.rmi.ssl.disable is set to 'true' 2020-12-11 11:33:45,630 INFO o.a.j.r.RmiUtils: Disabling SSL for RMI as server.rmi.ssl.disable is set to 'true' 2020-12-11 11:33:45,630 INFO o.a.j.s.BatchSampleSender: Using batching (client settings) for this run. Thresholds: num=100, time=60000 2020-12-11 11:33:45,630 INFO o.a.j.s.DataStrippingSampleSender: Using DataStrippingSampleSender for this run 2020-12-11 11:33:45,630 INFO o.a.j.r.RmiUtils: Disabling SSL for RMI as server.rmi.ssl.disable is set to 'true' 2020-12-11 11:33:45,630 INFO o.a.j.r.RmiUtils: Disabling SSL for RMI as server.rmi.ssl.disable is set to 'true' 2020-12-11 11:33:45,630 INFO o.a.j.r.RmiUtils: Disabling SSL for RMI as server.rmi.ssl.disable is set to 'true' 2020-12-11 11:33:45,630 INFO o.a.j.r.RmiUtils: Disabling SSL for RMI as server.rmi.ssl.disable is set to 'true' 2020-12-11 11:33:45,641 INFO o.a.j.r.RmiUtils: Disabling SSL for RMI as server.rmi.ssl.disable is set to 'true' 2020-12-11 11:33:45,641 INFO o.a.j.r.RmiUtils: Disabling SSL for RMI as server.rmi.ssl.disable is set to 'true' 2020-12-11 11:33:45,641 INFO o.a.j.s.BatchSampleSender: Using batching (client settings) for this run. Thresholds: num=100, time=60000 2020-12-11 11:33:45,641 INFO o.a.j.s.DataStrippingSampleSender: Using DataStrippingSampleSender for this run 2020-12-11 11:33:48,060 INFO o.a.j.e.ClientJMeterEngine: sent test to 192.168.1.135 basedir='.' 2020-12-11 11:33:48,060 INFO o.a.j.e.ClientJMeterEngine: Sending properties {} 2020-12-11 11:33:48,075 INFO o.a.j.e.ClientJMeterEngine: sent run command to 192.168.1.135 2020-12-11 11:33:48,075 INFO o.a.j.e.DistributedRunner: Remote engines have been started:[192.168.1.135] 2020-12-11 11:33:48,721 INFO o.a.j.g.u.JMeterMenuBar: setRunning(true, 192.168.1.135) 2020-12-11 11:35:49,030 INFO o.a.j.g.u.JMeterMenuBar: setRunning(false, 192.168.1.135)
    

    JMeter CLI interface:

    Creating summariser <summary> Created the tree successfully using fileExample.jmx Configuring remote engine: 192.168.1.135 Starting distributed test with remote engines: [192.168.1.135] @ Fri Dec 11 12:41:46 CET 2020 (1607686906826) Remote engines have been started:[192.168.1.135] Waiting for possible Shutdown/StopTestNow/HeapDump/ThreadDump message on port 4445 summary =      0 in 00:00:00 = ******/s Avg:     0 Min: 9223372036854775807 Max: -9223372036854775808 Err:     0 (0.00%) Tidying up remote @ Fri Dec 11 12:43:51 CET 2020 (1607687031041) ... end of run
    

    Question:
    So the question is basically what can be wrong to make the server recognize the start calls, send the end signal, but don't write the .jtl file.

    global:posted_in, Performance, Load, Stress Testing
  • Privacy Policy

    SOFTWARE-TESTING.COM collects and processes your personal information.

    Collecting data from users
    During the registration step you were asked to provide a username and email address, you can also optionally provide additional information to complete your user profile on this website. If you use Facebook or Google registration process, you will provide your first name, last name, email and profile picture to create your user account.

    Sharing your personal information

    • We use this information strictly to personalize your experience in SOFTWARE-TESTING.COM community, as well as to associate the posts you make to your user account.

    • We do not sell, trade, or rent Users personal identification information to others.

    • We retain this information for the life of your user account, and you are able to withdraw consent at any time by deleting your account.

    Your acceptance of these terms
    By using SOFTWARE-TESTING.COM, you signify your acceptance of this policy and terms of service.
    If you do not agree to this policy, please do not use our site.
    Your continued use of the site following the posting of changes to this policy will be deemed your acceptance of those changes.

    Contacting us
    If you have any questions or concerns, we encourage you to reach out to this forum's administrative team via email info@software-testing.com

    global:posted_in, About software-testing.com