Summary: | DurationAssertion does not seem to make difference between Main sample only and Main sample and sub-samples for time | ||
---|---|---|---|
Product: | JMeter - Now in Github | Reporter: | Philippe Mouawad <p.mouawad> |
Component: | Main | Assignee: | JMeter issues mailing list <issues> |
Status: | NEW --- | ||
Severity: | normal | CC: | dzmitry.kashlach, p.mouawad |
Priority: | P2 | ||
Version: | 2.8 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Bug Depends on: | 51939 | ||
Bug Blocks: | |||
Attachments: | Test Plan showing issue |
Description
Philippe Mouawad
2012-11-15 23:06:47 UTC
Created attachment 29819 [details]
Test Plan showing issue
(In reply to Philippe Mouawad from comment #0) > I may be wrong but I don't see in JMeterThread#checkAssertions code: > if (scopedAssertion.isScopeParent(scope) || > scopedAssertion.isScopeAll(scope) || scopedAssertion.isScopeVariable(scope)){ > processAssertion(parent, assertion); > } > Actually, this code is present in JMeterThread(lines 677-679). But as far as I understand from code, Duration Assertion is processed against parent+subsamples time anyway(if subsamples are present). This happens because SampleResult contains time not only for parent request, but for parent+subrequests. To my mind, changes in SampleResult are required. > To my mind, changes in SampleResult are required.
May be, splitting field SampleResult.elapsedTime into two ones(mainElapsedTime&childElapsedTime) will be good solution?
+1 Still seeing this issue in JMeter 3.x. Perhaps the UI element (radiobutton) for "Main sample only" can be removed/hidden from the Duration Assertion GUI until this can be resolved? This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2983 |