Thanks. On Fri, Aug 19, 2016 at 2:23 PM, sebb <[email protected]> wrote:
> AFAICT it is failing, provided that the total time is more than 11 seconds. > > That's not the case for tests 2A and 2B. > > Check the Tree View and/or add a Table listener to show the timings. > > On 19 August 2016 at 12:03, Sankar Das <[email protected]> wrote: > > ok. Then why Duration assertion is not failing? > > > > On Fri, Aug 19, 2016 at 1:53 PM, sebb <[email protected]> wrote: > > > >> Note that Assertions don't generate any sample results unless they fail. > >> > >> That does not mean that they have not run. > >> > >> On 19 August 2016 at 10:55, Sankar Das <[email protected]> > wrote: > >> > Thanks for the reply. > >> > > >> > Findings are below with : > >> > > >> > HTTP Sampler > >> > Duration Assertion > >> > Response Assertion > >> > View Results Tree > >> > > >> > > >> > 1. Without timeout in HTTP Sampler: > >> > > >> > Duration assertion :Assertion failure message: The operation lasted > too > >> > long: It took 733 milliseconds, but should not have lasted longer > than 11 > >> > milliseconds. > >> > Response Assertion :Assertion failure message: Test failed: text > expected > >> > to contain /NOT FOUND/ > >> > Response Data: Proper Response > >> > > >> > 2. With timeout HTTP Sampler: > >> > A: > >> > Timeout(milliseconds) > >> > connect :1 , Response:1 > >> > > >> > Duration assertion : Not Running > >> > Response Assertion :Assertion failure message: Test failed: text > expected > >> > to contain /NOT FOUND/ > >> > Response Data: org.apache.http.conn.ConnectTimeoutException: Connect > to > >> > www.myurl.com.com:80 timed out > >> > > >> > B: > >> > Timeout(milliseconds) > >> > connect :5 , Response:5 > >> > > >> > Duration assertion : Not Running > >> > Response Assertion :Assertion failure message: Test failed: text > expected > >> > to contain /NOT FOUND/ > >> > Response Data: org.apache.http.conn.ConnectTimeoutException: Connect > to > >> > www.myurl.com.com:80 timed out > >> > > >> > C: > >> > Timeout(milliseconds) > >> > connect :10 , Response:10 > >> > > >> > Duration assertion : Assertion failure message: The operation lasted > too > >> > long: It took 12 milliseconds, but should not have lasted longer than > 11 > >> > milliseconds. > >> > Response Assertion :Assertion failure message: Test failed: text > expected > >> > to contain /NOT FOUND/ > >> > Response Data: org.apache.http.conn.ConnectTimeoutException: Connect > to > >> > www.myurl.com.com:80 timed out > >> > > >> > D: > >> > Timeout(milliseconds) > >> > connect :1000 , Response:1000 > >> > > >> > Duration assertion : Assertion failure message: The operation lasted > too > >> > long: It took 12 milliseconds, but should not have lasted longer than > 11 > >> > milliseconds. > >> > Response Assertion :Assertion failure message: Test failed: text > expected > >> > to contain /NOT FOUND/ > >> > Response Data: Proper Response > >> > > >> > My query was > >> > > >> > *Irrespective of the result of the response data, the "Response > >> Assertion" > >> > is running. So why not the "Duration assertion".* > >> > > >> > Hope I am clear with my query. > >> > > >> > Thanks! > >> > > >> > > >> > > >> > > >> > On Fri, Aug 19, 2016 at 12:11 PM, sebb <[email protected]> wrote: > >> > > >> >> Duration assertion works for me when applied to a HTTP sample > timeout. > >> >> > >> >> But note that the sample result will have been marked as failed; this > >> >> may affect other test elements such as assertions. > >> >> > >> >> Try a very simple test plan with just: > >> >> > >> >> HTTP Sampler > >> >> Duration Assertion > >> >> View Results Tree > >> >> > >> >> > >> >> On 16 August 2016 at 18:23, Adrian Speteanu <[email protected]> > >> wrote: > >> >> > If you can obtain the entire time interval by adding the intended > >> request > >> >> > and pre/post actions into a single transaction controller, than any > >> >> > duration assertion you add as child of the controller should do > what > >> you > >> >> > say. But, again, I'm still fuzzy on what exactly is that you're > >> trying to > >> >> > do. > >> >> > > >> >> > Cheers, > >> >> > A > >> >> > > >> >> > On Tue, Aug 16, 2016 at 4:28 PM, Sankar Das < > >> [email protected]> > >> >> > wrote: > >> >> > > >> >> >> Add to this. > >> >> >> > >> >> >> If the "Response Assertion" can verify the response text > >> irrespective of > >> >> >> the sampler connection time than why not the "Duration Assertion" > >> wont > >> >> >> calculate the timing if the thread is timing out. > >> >> >> > >> >> >> PS: Do know that "Duration Assertion" will calculate the time of > the > >> >> >> sampler first than compare with the duration given. If the thread > is > >> >> >> waiting then it will also wait. > >> >> >> > >> >> >> Thanks! > >> >> >> > >> >> >> On Tue, Aug 16, 2016 at 4:07 PM, Sankar Das < > >> [email protected] > >> >> > > >> >> >> wrote: > >> >> >> > >> >> >> > Hi, > >> >> >> > > >> >> >> > Thanks a lot for the reply. > >> >> >> > > >> >> >> > Trying check the accessibility of some APIs on some intervals by > >> help > >> >> of > >> >> >> > Jenkins, Ant and JMeter and do some actions if they are not > >> >> >> accessible.Not > >> >> >> > the server response time. I guess from JMeter we can do it.Yes, > we > >> can > >> >> >> also > >> >> >> > do functional testing using JMeter although it acts like a > browser. > >> >> >> > > >> >> >> > > >> >> >> > Thanks! > >> >> >> > > >> >> >> > > >> >> >> > On Tue, Aug 16, 2016 at 3:40 PM, Adrian Speteanu < > >> [email protected] > >> >> > > >> >> >> > wrote: > >> >> >> > > >> >> >> >> I don't understand the use-case or why anyone would want to > >> include > >> >> any > >> >> >> >> timeouts in the response times if they're added by anything > else > >> >> other > >> >> >> >> than > >> >> >> >> the system under test. The purpose of the tool is to measure > >> server > >> >> side > >> >> >> >> response times (from just before starting a new connection to > the > >> >> point > >> >> >> >> just after receiving the last bit of the response), not the > >> >> measurement > >> >> >> >> tool's own processing/time-wait periods. > >> >> >> >> > >> >> >> >> That been said, I've seen use-cases where one might need to > >> calculate > >> >> >> the > >> >> >> >> total duration of an action that requires multiple/nested > requests > >> >> and > >> >> >> in > >> >> >> >> order to get the total value for this group, one can use the > >> >> transaction > >> >> >> >> controller and adding a listener that has this controller in > its > >> >> scope. > >> >> >> I > >> >> >> >> think it might have some options that might prove useful: > >> >> >> >> http://jmeter.apache.org/usermanual/component_reference. > >> >> >> >> html#Transaction_Controller > >> >> >> >> > >> >> >> >> I must insist though that a bigger problem would be the > >> requirements > >> >> and > >> >> >> >> making sure they are justified. > >> >> >> >> > >> >> >> >> Cheers, > >> >> >> >> A > >> >> >> >> > >> >> >> >> On Tue, Aug 16, 2016 at 3:11 PM, Sankar Das < > >> >> [email protected] > >> >> >> > > >> >> >> >> wrote: > >> >> >> >> > >> >> >> >> > Hi, > >> >> >> >> > > >> >> >> >> > *Scenario*: My requirement is to do some actions when the > >> assertion > >> >> >> >> fails. > >> >> >> >> > > >> >> >> >> > *Issue*:When the thread is timing out (have provided the > timeout > >> >> >> details > >> >> >> >> > in" HTTP Request Defaults", JMeter "Duration Assertion" is > not > >> >> >> >> calculating > >> >> >> >> > the timing of the timed out sampler. > >> >> >> >> > > >> >> >> >> > Hence not able to do the action. > >> >> >> >> > > >> >> >> >> > *Expected*. > >> >> >> >> > Response duration should be able to calculate the timeout > time > >> of > >> >> the > >> >> >> >> > sampler ,even if the sampler is timed-out. > >> >> >> >> > > >> >> >> >> > >> >> >> > > >> >> >> > > >> >> >> > >> >> > >> >> ------------------------------------------------------------ > --------- > >> >> To unsubscribe, e-mail: [email protected] > >> >> For additional commands, e-mail: [email protected] > >> >> > >> >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
