Hello, Currently majority of Extractors are based on syntax: - XPath, - Regex, - Boundary, - CSS / JQuery
Only JSON is based on format, but I remember it was due to JSON Path already being used. I think the issue with CSS/ JQuery is that name is maybe not clear to testers. Should it be CSS Selector extractor ? And should we by the way name JSON Extractor => JSON Path Extractor ? Regards On Thu, Aug 2, 2018 at 10:05 AM, Andrey Pokhilko <[email protected]> wrote: > HTML Extractor is also very generic name. > > Let's understand which naming tradition do we use consistently for > extractors - is it "by syntax used" or "by what it extracts"? Otherwise > users will be confused when use HTML Extractor and when Boundary > Extractor... > > I am for "by syntax used" since this is a tradition we have up to now > and it is less ambiguous. > > -- > > Andrey Pokhilko > > 02.08.2018 11:01, Jmeter Tea пишет: > > Regex Extractor is more generic, it can extract from any text (JSON, > plain, > > XML, ....) > > > > On Thu, Aug 2, 2018 at 10:57 AM, Andrey Pokhilko <[email protected]> wrote: > > > >> Hi, > >> > >> IMO name is fine, since it reflects the syntax. Regex Extractor also > >> extracts from HTML, XPath Extractor also extracts from HTML. > >> > >> -- > >> > >> Andrey Pokhilko > >> > >> 02.08.2018 08:51, Jmeter Tea пишет: > >>> It seems that CSS/JQuery Extractor name is a bit confusing, > >>> Because it actually used to extract *HTML *using CSS/JQuery syntax > >>> Isn't it better to rename it to HTML Extractor or HTML DOM Extractor ? > >>> > >>> Relevant question: > >>> https://stackoverflow.com/questions/51644320/jmeter-how- > >> to-use-the-jquery-not-css-extractor/51646040#51646040 > >> > > -- Regards Ubik Load Pack <http://ubikloadpack.com> Team Follow us on Twitter <http://twitter.com/ubikloadpack> Cordialement L'équipe Ubik Load Pack <http://ubikloadpack.com> Suivez-nous sur Twitter <http://twitter.com/ubikloadpack>
