Re: BUG 62536 / Introduce a kind of workflow for Load Testing (Record / Validate / Load Test)

Because one of best practices is to reduce Listeners and also Assertions It's better if a "disabled on no gui" option is added to all components, so different components can be disabled on non gui manually. Also can disable Debug Sampler(s) and other scripts used mainly for debugging On Wed, Jul 1

Re: Bug 61805 - Allow simple HTTP request

El mié., 18 jul. 2018 22:06, Philippe Mouawad escribió: > Hello, > I think it's a very good idea that would help newbies with JMeter. > > I think a simple way to implement it would be would be a menu in File: > > > Test URL > > User would just enter the URL and check and a test plan would be crea

buildbot failure in on jmeter-nightly

The Buildbot has detected a new failure on builder jmeter-nightly while building . Full details are available at: https://ci.apache.org/builders/jmeter-nightly/builds/1102 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave7_ubuntu Build Reason: The Nightly scheduler na

Build failed in Jenkins: JMeter-trunk #6851

See Changes: [pmouawad] Bug 61635 - Add a menu to restart JMeter Fix wrong class for logger Bugzilla Id: 61635 [pmouawad] Bug 61635 - Add a menu to restart JMeter Bugzilla Id: 61635 [pmouawad] Bug 62541: Allow __je

Build failed in Jenkins: JMeter Ubuntu #501

See Changes: [pmouawad] Bug 61635 - Add a menu to restart JMeter Fix wrong class for logger Bugzilla Id: 61635 [pmouawad] Bug 61635 - Add a menu to restart JMeter Bugzilla Id: 61635 [pmouawad] Bug 62541: Allow __

Build failed in Jenkins: JMeter Windows #1111

See Changes: [pmouawad] Bug 61635 - Add a menu to restart JMeter Fix wrong class for logger Bugzilla Id: 61635 [pmouawad] Bug 61635 - Add a menu to restart JMeter Bugzilla Id: 61635 [pmouawad] Bug 62541: Allow

Re: Bug 61805 - Allow simple HTTP request

Hello, I think it's a very good idea that would help newbies with JMeter. I think a simple way to implement it would be would be a menu in File: > Test URL User would just enter the URL and check and a test plan would be created: Test Plan |Thread Group |

buildbot failure in on jmeter-trunk

The Buildbot has detected a new failure on builder jmeter-trunk while building . Full details are available at: https://ci.apache.org/builders/jmeter-trunk/builds/3868 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave1_ubuntu Build Reason: The AnyBranchScheduler sched

Jenkins build is back to normal : JMeter-trunk #6850

See

Re: [GitHub] jmeter issue #393: Jmeter 2.4.x

On 18 July 2018 at 16:01, Philippe Mouawad wrote: > On Wednesday, July 18, 2018, sebb wrote: > >> It looks like JMeter PMC don't have karma to close other people's PRs. >> [That's probably because git is only a mirror.] > > > can’t this be changed by the way ? Sorry, no idea. Try asking Infra.

Re: [GitHub] jmeter issue #393: Jmeter 2.4.x

On Wednesday, July 18, 2018, sebb wrote: > It looks like JMeter PMC don't have karma to close other people's PRs. > [That's probably because git is only a mirror.] can’t this be changed by the way ? It would makes things easier for us. > > If the originator does not respond, try making a dumm

Re: [GitHub] jmeter issue #393: Jmeter 2.4.x

It looks like JMeter PMC don't have karma to close other people's PRs. [That's probably because git is only a mirror.] If the originator does not respond, try making a dummy commit with the appropriate 'this fixes #nnn' comment. On 18 July 2018 at 15:41, pmouawad wrote: > Github user pmouawad co

Re: Generating report by default in NON GUI mode

On Monday, July 16, 2018, Antonio Gomes Rodrigues wrote: > Hi Philippe, > > It's a good idea but I think we need to: > > Optimize the performance Felix has been improving this > > Improve the output during the generation to display something to the user a kind of windows progress bar :) as a

Re: BUG 62536 / Introduce a kind of workflow for Load Testing (Record / Validate / Load Test)

On Monday, July 16, 2018, Antonio Gomes Rodrigues wrote: > Hi, > > - Maybe the recorder should be here by default and not deletable and a > record button could then be added as a menu > +1 > > - And finally, since a Thread Group is the mandatory component to add > Test items, it should be here by

Re: SubResult Naming Policy

Hello, Any feedback ? Can I commit it ? Thanks On Tuesday, July 17, 2018, Philippe Mouawad wrote: > Hello, > I attached a patch to: > > - https://bz.apache.org/bugzilla/show_bug.cgi?id=62550 > > > Please review and comment. > > Test with embedded resource works. > Regards > > On Tue, Jul 17, 2

[GitHub] jmeter issue #393: Jmeter 2.4.x

Github user pmouawad commented on the issue: https://github.com/apache/jmeter/pull/393 Hello, What is the purpose of this Pr ? It looks like it’s empty. Can you close it please ? Thank you ---

buildbot success in on jmeter-trunk

The Buildbot has detected a restored build on builder jmeter-trunk while building . Full details are available at: https://ci.apache.org/builders/jmeter-trunk/builds/3866 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave1_ubuntu Build Reason: The AnyBranchScheduler sc