> > You have to set the assertion as a child of the sampler, if you want to > verify the result of that sampler. > So, the assertion must go into the fragment. >
that kills the reusability of the included test fragment. Mine is a generic test fragment to get a piece of a log file. I don't want to add an assertion there. My question in the end is how can I retrieve the response of the sampler in the included test fragment from the "parent" test plan. I don't like that a parent test plan must know what variable name was used by the included test fragment. It's like if in a programming language, the calling function would have access to the local variables (and not the result) of the called function. Sergio: a volte mi dico che forse dovrei provare con un altro programma...
