On Tue, Jan 29, 2019 at 11:43 AM Vladimir Sitnikov < [email protected]> wrote:
> Philippe> But while it was rather straightforward to implement through > Maven, it's a > Philippe> bit more complex in core JMeter. > > I guess the most challenging part is to incorporate "Non Functional > Requirements" to JMeter UI. > > For instance: > 1) Should it be a separate UI or should each sampler have "NFR" section? > No convictions. For simplicity, I thought about a dedicated config element "SLA Rules": + One place for all - But desynch can happen if you rename transactions / sampler and forget to update If we do as you propose, no desync but rules are spread in the whole test plan, we need to consider also Transaction Controller. > 2) Should there be a warning in case NFR did not fire (e.g. user > specified "ligon.pct90 < 1sec" and actual transaction has name of > "login")? > Yes, at least in logs > 3) Should it warn for conflicting requirements? (e.g. *.pct90<1sec > + login.pct90<5sec) > I would say, login.pct90 is an override of general rule. But I didn't dig in implementation details yet. 5) Should it allow for rule inherinance? e.g. > "simple.pages.pct90<1sec, login is a "simple page". > Someone please stop me :) > STOP ! :-) Let's start and work incrementally > > Vladimir > -- Cordialement. Philippe Mouawad.
