You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2012/05/30 17:48:40 UTC

[Bug 53330] New: Add an option to run the test in 'Dry Run' Mode

https://issues.apache.org/bugzilla/show_bug.cgi?id=53330

          Priority: P2
            Bug ID: 53330
          Assignee: issues@jmeter.apache.org
           Summary: Add an option to run the test in 'Dry Run' Mode
          Severity: enhancement
    Classification: Unclassified
                OS: All
          Reporter: oliver_lloyd@hotmail.com
          Hardware: All
            Status: NEW
           Version: 2.7
         Component: Main
           Product: JMeter

I find that I often need to run a quick test of the test by executing each
thread group once, using just one user. This tells me that there are no major
issues with the testplan without actually running too much load against the
AUT.

To execute such a dry run I currently have to reset a lot of values in the
testplan which is time consuming and prone to error.

It would be useful to have a feature whereby the test could be executed in dry
run mode. Such a mode could include:

1. Run each enabled thread group once, with one user.
2. Ignore any timers.
3. Ignore any throughput controllers.
4. Ignore other controllers that are designed to shape traffic.
5. No ramp up period.
6. Debug mode for logging(?).
7. Possibly an option to reduce connection timeouts - in dry run mode you don't
want to wait 30 seconds to find out something is not working.
8. An option to use this mode from the command line!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 53330] Add an option to run the test in 'Dry Run' Mode

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=53330

--- Comment #3 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
I wonder if we should touch ThroughputControllers as in fact they don't control
throughput.
Do you have a case in mind where it would be needed ?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 53330] Add an option to run the test in 'Dry Run' Mode

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=53330

Philippe Mouawad <p....@ubik-ingenierie.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #5 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
After discussion on mailing list , it seems it's too much work for a feature
that's not likely to be much used.

Closing as won't fix unless we get more arguments.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 53330] Add an option to run the test in 'Dry Run' Mode

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=53330

Philippe Mouawad <p....@ubik-ingenierie.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO
                 CC|                            |p.mouawad@ubik-ingenierie.c
                   |                            |om

--- Comment #1 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
(In reply to comment #0)
> I find that I often need to run a quick test of the test by executing each
> thread group once, using just one user. This tells me that there are no
> major issues with the testplan without actually running too much load
> against the AUT.
> 
> To execute such a dry run I currently have to reset a lot of values in the
> testplan which is time consuming and prone to error.
> 
> It would be useful to have a feature whereby the test could be executed in
> dry run mode. Such a mode could include:
> 
> 1. Run each enabled thread group once, with one user. 
OK
> 2. Ignore any timers.
OK
> 3. Ignore any throughput controllers.
This would kind of modify behaviour, and not test its children.
Better to replace by SimpleController ?
> 4. Ignore other controllers that are designed to shape traffic.
Same thing, Better to replace by SimpleController ?
> 5. No ramp up period.
OK
> 6. Debug mode for logging(?).
OK
> 7. Possibly an option to reduce connection timeouts - in dry run mode you
> don't want to wait 30 seconds to find out something is not working.
Maybe
> 8. An option to use this mode from the command line!
OK

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 53330] Add an option to run the test in 'Dry Run' Mode

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=53330

--- Comment #4 from oliver lloyd <ol...@hotmail.com> ---
We use throughput controllers to mimic dropoff rates as people move through
payment and registration journeys. We have various levels of nested controllers
that restrict, using a percentage, the volume of threads that continue.

The problem is that in order to quickly verify functionality we need to change
each percentage to 100%, for each controller. Then, later, we need to set them
back to their correct values.

But I can see how this is a specific case and the problem might be that there
are other ways to use the throughput controller (total executions, not
percentage) so I appreciate this is not as simple as the other features.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 53330] Add an option to run the test in 'Dry Run' Mode

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=53330

--- Comment #2 from oliver lloyd <ol...@hotmail.com> ---
Re: Simple Controllers. Yes, agreed. Temporarily changing a Throughput (or
similar) controller to a Simple controller for Dry Run mode would achieve the
desired goal of forcing the child requests to be executed.

-- 
You are receiving this mail because:
You are the assignee for the bug.