Jarno Pelkonen (Bug 14762):
JMeter needs an "assertion defaults" component that can be put under containing
containg controller (= any sampler or Thread group).
This easies building up test cases that do several requests and most of the
responses are validated with the same logic. This is a common case with HTTP
test cases.
"Assertion defaults" component could be a containing component, i.e. it would
contain the actual assertions. Responses would be validated against:
all assertions defined for the individual request (= the current way)
plus againt all the assertions in the "assertion defaults" components in the
request's parent nodes. By this way a Jmeter user could define default
assertions at Thread group level and then more detailed assertions for samplers
under the thread group.
Sebb (migrated from Bugzilla):
This seems to happen by default now; also copy and paste works, so I'm closing
the call, but feel free to re-open if there's something I've missed
Jarno Pelkonen (Bug 14762): JMeter needs an "assertion defaults" component that can be put under containing containg controller (= any sampler or Thread group).
This easies building up test cases that do several requests and most of the responses are validated with the same logic. This is a common case with HTTP test cases.
"Assertion defaults" component could be a containing component, i.e. it would contain the actual assertions. Responses would be validated against:
Votes in Bugzilla: 1 OS: All