Forum Discussion

AndyHughes's avatar
AndyHughes
Regular Contributor
14 years ago

Distributed testing on Agents

I have a load test set up and am trying to run it on an agent. I have the agent installed on a VM and have launched the agent on the VM which appers to be 'listening'.

When I run the test in distributed mode I have no idea if anything is actually happening. I thought the results would maybe be displayed on my local machine (There is a setting on the statistics component to view the statistics from certain agents or aggregated data) but either way this displays nothing and the table logs display nothing as does the actual runner component.

So how do I check a) If anything is actually happening at all, and b) where the results are for each agent?

and to preempt the inevitible 'nothing is happening' - what am I doing wrong?
  • AndyHughes's avatar
    AndyHughes
    Regular Contributor
    14 years ago
    Yeah unfortunately I've done all of this. But still nothing?? The LED isn't lit on the actual test case itself, but the agent is ON and the test case is deployed.
  • dmltn84's avatar
    dmltn84
    Occasional Contributor
    14 years ago
    I have similar problem.

    1. I create Web Service test in Soap UI (Windows 7)
    2. I create Load Test based on this test in Load UI
    3. I run load test in local mode and observe resource utilization. Increasing load increases utilization.
    4. I deploy agent on Fedora OS, connect it in controller and it connects (at least Load UI controller displayes icon that it is connected). I run test in distributed mode and resource utilization on the agent machine is not changing while I change number of threads.

    LoadUI claims that agent is connected and requests are sent, but resource utilization is stuck on agent machine. I tried from 1 to 3000 threads per second - result is the same.

    How do I debug such issues?
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    14 years ago
    Hi Andy,

    Just wanted to make sure that you have seen this.

    Does that apply to you (are you using a nightly build)?


    Henrik
    SmartBear Software
  • AndyHughes's avatar
    AndyHughes
    Regular Contributor
    14 years ago
    Ah yes I think I am. Ok, I may wait 'till LoadUI2.0 then. Thanks
  • bennythedroid's avatar
    bennythedroid
    Occasional Contributor
    14 years ago
    I figured I would go ahead and attach myself to this thread rather than start another one.

    I can't get agents to do anything, in 1.5 stable or in the nightlies. I set up agents on some other machines, I autodetected the agents from loadui once I got them running in the other machines. I dragged my test case over onto the agents, and then ran the load test. The red led light on the agents blinks while the test is running. Does that mean something is wrong or that it is supposedly running?

    Either way, the agents do nothing. The testing involves sending emails and sms messages. As a very simple test, I ran 1 request (email)/sec for 30 seconds, using just one agent. Based on the agent functionality, I would expect to then see approximately 60 new emails at the end of 30 seconds (factoring in a little more time for the emails to actually get to my account). 30 for the loadui on the primary machine, and 30 for the agent. I only ever see 30 emails.

    Any suggestions?
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    14 years ago
    Hello,

    If you run in Local mode, TestCases will only execute on the local machine -- so 30 requests seem correct in that case.
    If you run in Distributed mode, TestCases will only execute on the agents to which they are distributed -- so 30 requests seem correct in that case as well.
    This is explained here in the documentation.

    If you want to run a TestCase on the "primary" machine (the controller) in distributed mode, you have to start a loadUI agent on that machine.

    Regards

    Henrik
    SmartBear Software