jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Podelko <apode...@yahoo.com.INVALID>
Subject Re: [OpenIV:0551] Re: Bugzilla Enhancement: "Auto-Correlation as core functionality in JMeter"
Date Wed, 21 Aug 2019 17:42:47 GMT
 Completely agree. It would be a great benefit for the community and will move JMeter to the
next level (from the enterprise point of view).

According to my experience, if rules are well defined, the script may be correlated automatically
(with rather few exceptions). But ability to rollback the correlation and check the places
it suggest to correlate interactively would be additional  bonuses.

Thanks,Alex

    On Tuesday, August 20, 2019, 4:01:51 AM EDT, Takashi Imoto <t-imoto@ak.jp.nec.com>
wrote:  
 
 To: Alexander-san.

Thank you for comment us.
It's a good suggestion, and we are considering this too.

> As I am working with same products again and again, I don't need to auto-correlate or
record it twice

Yes, I have same experience.
I think most of correlation value like session or state, related to framework or some library.
So exporting correlation file is useful, and this rule file stores correlation in same products.

So I have thinking following scenario.

1st time.
Find correlation value by recording scripts 2 times, and exporting correlation variable and
expression as correlation rule file.
And named as framework or products rule file.

2nd time and after that.
Record scripts once and load rule file, then list up candidate of correlation.
Select and replace correlation variable.

I think this approach, can save your efforts.

Additional value,
If framework and products developer provide rule files, all framework and products user can
use this file and save efforts.
Common framework rule files can be distributed by the community.

So what do you think about it ?

Thanks Imoto.

------------------------------
NEC Software Division
Imoto:  t-imoto@ak.jp.nec.com



> -----Original Message-----
> From: Alexander Podelko <apodelko@yahoo.com>
> Sent: Friday, August 9, 2019 11:40 PM
> To: dev@jmeter.apache.org
> Cc: necti_openiv_swe <necti_openiv@swe.jp.nec.com>
> Subject: [OpenIV:0551] ##freemail## Re: Bugzilla Enhancement:
> "Auto-Correlation as core functionality in JMeter"
> 
> Hello,
> 
> 
> On a related enhancement (if I read it correctly, it isn't covered by that
> enhancement - but for me it appears the largest issue JMeter has at the
> moment): having a correlation library with known correlation rules would be a
> great help.
> 
> As I am working with same products again and again, I don't need to
> auto-correlate or record it twice - I know everything I need to correlate (and
> have correlation libraries in OATS and LoadRunner - which do all the
> correlation for me at once). But making that manually in dozens or even
> hundreds places is a real pain....
> 
> 
> See an older discussion on the subject:
> https://www.mail-archive.com/user@jmeter.apache.org/msg10181.html
> 
> Thanks,
> Alex
> 
> 
> 
> On Thursday, August 8, 2019, 4:40:16 AM EDT, Takashi Imoto
> <t-imoto@ak.jp.nec.com> wrote:
> 
> 
> To: Philippe-san.
> 
> Thank you for your feedback.
> 
> We understand following points, we will check the feasibility and confirm
> accordingly.
> 
> > - if html, try using css selector extractor if possible
> > - if json, json path
> > - if xml, xpath2
> > - otherwise boundary extractor or regex extractor
> 
> 
> > Second, try to follow a naming convention for autocorrelated variables
> > to easily detect them
> 
> We agree with this points, and we will suggest naming convention and take
> community feedback.
> 
> Thanks.
> Takashi Imoto.
> 
> 
> > -----Original Message-----
> > From: Philippe Mouawad <philippe.mouawad@gmail.com
> > <mailto:philippe.mouawad@gmail.com> >
> > Sent: Thursday, August 8, 2019 5:25 PM
> > To: dev@jmeter.apache.org <mailto:dev@jmeter.apache.org>
> > Cc: necti_openiv_swe <necti_openiv@swe.jp.nec.com
> > <mailto:necti_openiv@swe.jp.nec.com> >
> > Subject: Re: Bugzilla Enhancement: "Auto-Correlation as core
> > functionality in JMeter"
> >
> > Hello,
> > As first note, I would try to not only limit extractors to regex but:
> >
> > - if html, try using css selector extractor if possible
> > - if json, json path
> > - if xml, xpath2
> > - otherwise boundary extractor or regex extractor
> >
> > Second, try to follow a naming convention for autocorrelated variables
> > to easily detect them
> >
> > Regards
> > On Thursday, August 8, 2019, Takashi Imoto <t-imoto@ak.jp.nec.com
> <mailto:t-imoto@ak.jp.nec.com> > wrote:
> >
> > > To: Mr. Philippe
> > >
> > > Thank you for quick response.
> > > We are happy to contribute to community.
> > >
> > > We have written approach and use case below tickets.
> > > <https://bz.apache.org/bugzilla/show_bug.cgi?id=63640>
> > >
> > > Could you please give me the feedback on our approach?
> > > Accordingly we will implemented and submit PR.
> > >
> > > We have already done the prototype, if you want to try the
> > > functionality, we can share that.
> > >
> > > Thanks.
> > > Takashi Imoto.
> > >
> > > > -----Original Message-----
> > > > From: Philippe Mouawad <pmouawad@apache.org
> > > > <mailto:pmouawad@apache.org> >
> > > > Sent: Thursday, August 8, 2019 4:28 PM
> > > > To: dev@jmeter.apache.org <mailto:dev@jmeter.apache.org>
> > > > Cc: necti_openiv_swe <necti_openiv@swe.jp.nec.com
> > > > <mailto:necti_openiv@swe.jp.nec.com> >
> > > > Subject: Re: Bugzilla Enhancement: "Auto-Correlation as core
> > > functionality in
> > > > JMeter"
> > > >
> > > > Hello,
> > > >
> > > > Thanks for your proposal.
> > > > This surely interests the community.
> > > > Please discuss conception on this list and make a PR on github.
> > > >
> > > > Regards
> > > > On Thursday, August 8, 2019, Takashi Imoto <t-imoto@ak.jp.nec.com
> > > > <mailto:t-imoto@ak.jp.nec.com> >
> > > wrote:
> > > >
> > > > > Hi Teams.
> > > > >
> > > > > To enhance usability of JMeter, NEC create new feature and bug
> > > > > fix in-house.
> > > > > And we want to contribute these features to the community.
> > > > >
> > > > > Last time, our company contributed fix patch about encoding issue.
> > > > >
> > > > > Bug63129-JMeter can not identify encoding during first time page
> > > > > submission.
> > > > > Based partly on analysis and PR made by Naveen Nandwani
> > > > > (naveen.nandwani@
> > > > > india.nec.com)
> > > > >
> > > > > And now we prototyped the feature that enable find correlation
> > > > > variable and set regular expression.
> > > > > We tried this feature in-house, and we can easily create and
> > > > > modify scripts.
> > > > >
> > > > > For detail we post as Enhancement as following.
> > > > >
> > > > > <https://bz.apache.org/bugzilla/show_bug.cgi?id=63640>
> > > > >
> > > > > Our company want to contribute this feature to the community and
> > > > > have plan to post PR.
> > > > >
> > > > > If team interested this, please give us feedback and request us PR.
> > > > >
> > > > > Thanks.
> > > > > Takashi Imoto.
> > > > >
> > > > > ------------------------------
> > > > > NEC
> > > > > Takashi Imoto:  t-imoto@ak.jp.nec.com
> > > > > <mailto:t-imoto@ak.jp.nec.com>
> > > > >
> > > > > https://www.nec.com/
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Ankur Gupta <ankur.gupta1@india.nec.com
> > > > > > <mailto:ankur.gupta1@india.nec.com> >
> > > > > > Sent: Tuesday, August 6, 2019 6:47 PM
> > > > > > To: dev@jmeter.apache.org <mailto:dev@jmeter.apache.org>
> > > > > > Subject: Bugzilla Enhancement: "Auto-Correlation as core
> > > > > > functionality in JMeter"
> > > > > >
> > > > > > Hello,
> > > > > >
> > > > > > We have raised one enhancement related to "Auto-Correlation
as
> > > > > > core functionality in JMeter" with below Bugzilla URL:
> > > > > >
> > > > > > https://bz.apache.org/bugzilla/show_bug.cgi?id=63640
> > > > > >
> > > > > > Requested Apache community members to provide their feedback
> > > > > > and suggestions on this enhancement.
> > > > > >
> > > > > > Thanks,
> > > > > > Ankur Gupta
> > > > > > ________________________________ The contents of this e-mail
> > > > > > and any attachment(s) are confidential and intended for the
> > > > > > named
> > > > > > recipient(s) only. It shall not attach any
> > > > > liability on the
> > > > > > originator or NECTI or its affiliates. Any views or opinions
> > > > > > presented
> > > > > in this
> > > > > > email are solely those of the author and may not necessarily
> > > > > > reflect the
> > > > > opinions
> > > > > > of NECTI or its affiliates. Any form of reproduction,
> > > > > > dissemination,
> > > > > copying,
> > > > > > disclosure, modification, distribution and / or publication
of
> > > > > > this
> > > > > message
> > > > > > without the prior written consent of the author of this e-mail
> > > > > > is
> > > > > strictly
> > > > > > prohibited. If you have received this email in error please
> > > > > > delete it
> > > > > and notify the
> > > > > > sender immediately.
> > > > >
> > > > >
> > >
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.

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