jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philippe Mouawad <philippe.moua...@gmail.com>
Subject Re: XPath Extractor : Drop Tidy Option
Date Sat, 18 Nov 2017 22:27:39 GMT
On Sat, Nov 18, 2017 at 11:19 PM, sebb <sebbaz@gmail.com> wrote:

> On 16 November 2017 at 19:20, Philippe Mouawad
> <philippe.mouawad@gmail.com> wrote:
> > Hello,
> > Tidy option AFAIK used to allow using XPath Extractor for HTML.
> > I don't think it's needed anymore since we have CSS/JQuery extractor
> which
> > is:
> > - Up to date
> > - Powerful
> > - Performing much better than XPath
> >
> > I propose to drop tidy options from XPath.
> > I even propose to think about dropping jtidy library which would mean :
> >
> >    - Either Dropping AnchorModifier or finding a better alternative to
> >    jtidy to it if it's useful
> >
> > IMO, we should drop it, as it doesn't work  with Distributed testing as
> it
> > requires keeping the previous SampleResult response Data to be able to
> work
> > which Stripping mode clears.
>
> Are you sure about that?
>
Yes, it is even documented in a note.
To be clear,
PreProcessor of Sampler N+1 requires access to Sample Result of Sampler N
which would be stripped in distributed mode.
It affects  Link Parser and Re-writing Modifier:
-
http://jmeter.apache.org/usermanual/component_reference.html#HTML_Link_Parser
-
http://jmeter.apache.org/usermanual/component_reference.html#HTTP_URL_Re-writing_Modifier

Surely that would break all PostProcessors that process response data?
>
No, because the problem is due to access to N-1 sampler's response data,
not current N Sampler's response data

>
> If it is the case, then that is a bug that needs to be fixed.
>
> > --
> > Cordialement.
> > Philippe Mouawad.
>



-- 
Cordialement.
Philippe Mouawad.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message