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

2018-07-18 Thread Jmeter Tea
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 18, 2018 at 5:43 PM, Philippe Mouawad <
philippe.moua...@gmail.com> wrote:

> 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 default
> > +1
> >
> > About  ignore View Results Tree on non GUI tests, I am not ok because
> > sometime I use "Log/Display Only on Errors" to have a "screenshot on
> > errors" to debug easily my script/dataset
>
>
>
> Maybe this would be a special view results tree that is ignored in non gui
> mode ?
>
> >
> > Antonio
> >
> >
> > Le dim. 15 juil. 2018 à 15:27, Jmeter Tea  a écrit
> :
> >
> > > +1
> > > But need to ignore View Results Tree (by default?) on non GUI tests
> > > (Important best practice in not to use View Results Tree/Listeners in
> non
> > > GUI)
> > > Notice existing Issue 62495  Add option to disable View Results
> > > Tree/Listeners in non GUI
> > >
> > > On Sun, Jul 15, 2018 at 4:04 PM, Philippe Mouawad <
> > > p.moua...@ubik-ingenierie.com> wrote:
> > >
> > > > Hello,
> > > > This has been opened as a bug and discussion was request, so putting
> it
> > > > here:
> > > >
> > > > 
> > > > 
> > > >
> > > > Today compared to other commercial load test tools, it may not be
> > > > obvious to users how to:
> > > > - Record
> > > > - validate
> > > > - Load Test
> > > >
> > > > This issue is to tackle the item and see what can be proposed.
> > > >
> > > >
> > > > For example:
> > > >
> > > > - Maybe the recorder should be here by default and not deletable and
> a
> > > > record button could then be added as a menu
> > > > - Also, why not always have by default a View Results Tree that is
> > > > used for Debugging a script
> > > > - And finally, since a Thread Group is the mandatory component to add
> > > > Test items, it should be here by default
> > > >
> > > >
> > > > 
> > > > 
> > > >
> > > > --
> > > > Regards.
> > > > Philippe Mouawad.
> > > >
> > >
> >
>
>
> --
> Cordialement.
> Philippe Mouawad.
>


Re: Bug 61805 - Allow simple HTTP request

2018-07-18 Thread Ralf Roeber
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 created:
> Test Plan
>   |Thread Group
>|--- HTTP Request with URL in path
>   | -- Header Manager with User-Agent
> set to ApacheJMeter
>   | View Results Tree
>
>
> What's your thoughts ?
>

Add variables to steer threads, http request and assertion
Add a CookieManager
Add a Loop
Add an assertion

If you use an URL from Jmeter-Website as predefined in variables to call in
http request, then Jmeter is calling home and one might understand more
about it's usage.



> Regards
>
> On Wed, Dec 6, 2017 at 7:27 AM, Or Mark  wrote:
>
> > I need your opinions about an enhancement I opened.
> >
> > I want to be able to execute Sampler (especially HTTP) on demand without
> > execute full test.
> >
> > This can be done in postman or in blazemeter ( or calling cUrl ).
> >
> > I want to know what is the scope of the change can be. Beacause it can be
> > very wide or/and specific,
> >
> > I'm suggesting adding a Send button in Sampler, but it can be on
> hierarchy
> > tree or on right click on a Sampler.
> >
> > Easiest option is to send url as is inside path.
> >
> > Second option is to send all attributes of Sampler as is.
> >
> > Third option is to evaluate all variables and functions in Sampler which
> > means to load variables and properties in Test plan/Thread group level.
> >
> > Thank you in advanced,
> > Ori marko
> >
>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>


buildbot failure in on jmeter-nightly

2018-07-18 Thread buildbot
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 named 'jmeterNightly' triggered this build
Build Source Stamp: [branch jmeter/trunk] HEAD
Blamelist: 

BUILD FAILED: failed shell_5

Sincerely,
 -The Buildbot





Build failed in Jenkins: JMeter-trunk #6851

2018-07-18 Thread Apache Jenkins Server
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 __jexl3, __jexl2 function to support new syntax as 
'var x;'. 
Contributed by orimarko
Bugzilla Id: 62541

--
[...truncated 148.03 KB...]
  [javadoc] Loading source files for package org.apache.jmeter.modifiers...
  [javadoc] Loading source files for package org.apache.jmeter.modifiers.gui...
  [javadoc] Loading source files for package org.apache.jmeter.sampler...
  [javadoc] Loading source files for package org.apache.jmeter.sampler.gui...
  [javadoc] Loading source files for package org.apache.jmeter.thinktime...
  [javadoc] Loading source files for package 
org.apache.jmeter.timers.poissonarrivals...
  [javadoc] Loading source files for package org.apache.jmeter.validation...
  [javadoc] Loading source files for package 
org.apache.jmeter.visualizers.backend.graphite...
  [javadoc] Loading source files for package 
org.apache.jmeter.visualizers.backend.influxdb...
  [javadoc] Loading source files for package 
org.apache.jmeter.visualizers.utils...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.http.api.auth...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.http.config...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.http.config.gui...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.http.control...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.http.control.gui...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.http.gui...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.http.modifier...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.http.modifier.gui...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.http.parser...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.http.proxy...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.http.proxy.gui...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.http.sampler...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.http.sampler.hc...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.http.util...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.http.util.accesslog...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.http.visualizers...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.ftp.config.gui...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.ftp.control.gui...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.ftp.sampler...
  [javadoc] Loading source files for package org.apache.jmeter.protocol.jdbc...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.jdbc.config...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.jdbc.processor...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.jdbc.sampler...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.java.config...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.java.config.gui...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.java.control.gui...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.java.sampler...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.java.test...
  [javadoc] Loading source files for package org.apache.jorphan.collections...
  [javadoc] Loading source files for package org.apache.jorphan.exec...
  [javadoc] Loading source files for package org.apache.jorphan.gui...
  [javadoc] Loading source files for package org.apache.jorphan.gui.layout...
  [javadoc] Loading source files for package org.apache.jorphan.io...
  [javadoc] Loading source files for package org.apache.jorphan.logging...
  [javadoc] Loading source files for package org.apache.jorphan.math...
  [javadoc] Loading source files for package org.apache.jorphan.reflect...
  [javadoc] Loading source files for package org.apache.jorphan.test...
  [javadoc] Loading source files for package org.apache.jorphan.util...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.ldap.config.gui...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.ldap.control.gui...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.ldap.sampler...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.tcp.config.gui...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.tcp.control.gu

Build failed in Jenkins: JMeter Ubuntu #501

2018-07-18 Thread Apache Jenkins Server
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 __jexl3, __jexl2 function to support new syntax as 
'var x;'. 
Contributed by orimarko
Bugzilla Id: 62541

[pmouawad] Bug 62554 - BoundaryExtractor : Field to check is not reset
Bugzilla Id: 62554

[fschumacher] Don't use a colon as part of the "tab" string when indenting JSON 
in RenderAsJSON.

Bugzilla Id: 62545

--
[...truncated 438.49 KB...]
  [jar] Building jar: 

  [jar] Building jar: 

  [jar] Building jar: 

  [jar] Building jar: 

  [jar] Building jar: 

  [jar] Building jar: 

  [jar] Building jar: 

  [jar] Building jar: 

  [jar] Building jar: 

  [jar] Building jar: 

  [jar] Building jar: 

  [jar] Building jar: 

  [jar] Building jar: 

  [jar] Building jar: 


package:

_check_3rdparty:

_message_3rdParty:

init-version:
 [echo] jmeter.version = 4.1-SNAPSHOT
 [echo] display.version = 4.1-SNAPSHOT r1836226
 [echo] implementation.version = 4.1-SNAPSHOT r1836226

compile-jorphan:

compile-core:

compile-components:

compile-functions:

compile-http:

compile-ftp:

compile-jdbc:

compile-java:

compile-ldap:

create-mail-dir:

compile-mail:

compile-tcp:

compile-protocols:

compile-junit:

compile-jms:

compile-native:

compile-mongodb:

compile:

compile-tests:
[mkdir] Created dir: 

[javac] Compiling 190 source files to 

[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
  [groovyc] Compiling 22 source files to 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 


Build failed in Jenkins: JMeter Windows #1111

2018-07-18 Thread Apache Jenkins Server
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 __jexl3, __jexl2 function to support new syntax as 
'var x;'. 
Contributed by orimarko
Bugzilla Id: 62541

[pmouawad] Bug 62554 - BoundaryExtractor : Field to check is not reset
Bugzilla Id: 62554

[fschumacher] Don't use a colon as part of the "tab" string when indenting JSON 
in RenderAsJSON.

Bugzilla Id: 62545

--
[...truncated 525.60 KB...]
   [jmeter] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
explanation.
   [jmeter] SLF4J: Actual binding is of type 
[org.apache.logging.slf4j.Log4jLoggerFactory]
   [jmeter] Creating summariser 
   [jmeter] Created the tree successfully using testfiles/SlowCharsFeature.jmx
   [jmeter] Starting the test @ Wed Jul 18 21:27:06 UTC 2018 (1531949226530)
   [jmeter] Waiting for possible Shutdown/StopTestNow/Heapdump message on port 
4445
   [jmeter] Jul 18, 2018 9:27:06 PM java.util.prefs.WindowsPreferences 
   [jmeter] WARNING: Could not open/create prefs root node 
Software\JavaSoft\Prefs at root 0x8002. Windows RegCreateKeyEx(...) 
returned error code 5.
   [jmeter] summary +  4 in 00:00:24 =0.2/s Avg:  5867 Min:   522 Max: 
11669 Err: 0 (0.00%) Active: 1 Started: 1 Finished: 0
   [jmeter] summary =  4 in 00:00:24 =0.2/s Avg:  5867 Min:   522 Max: 
11669 Err: 0 (0.00%)
   [jmeter] Tidying up ...@ Wed Jul 18 21:27:31 UTC 2018 (1531949251154)
   [jmeter] ... end of run
 [echo] SlowCharsFeature_Java output files compared OK

batchtest:
 [echo] Starting TestKeepAlive with file TestKeepAlive.jmx using -X 
-Jdummy=dummy
   [jmeter] SLF4J: Class path contains multiple SLF4J bindings.
   [jmeter] SLF4J: Found binding in 
[jar:file:/F:/jenkins/jenkins-slave/workspace/JMeter%20Windows/trunk/lib/log4j-slf4j-impl-2.11.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
   [jmeter] SLF4J: Found binding in 
[jar:file:/F:/jenkins/jenkins-slave/workspace/JMeter%20Windows/trunk/lib/opt/activemq-all-5.15.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
   [jmeter] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
explanation.
   [jmeter] SLF4J: Actual binding is of type 
[org.apache.logging.slf4j.Log4jLoggerFactory]
   [jmeter] Jul 18, 2018 9:27:33 PM java.util.prefs.WindowsPreferences 
   [jmeter] Creating summariser 
   [jmeter] Created the tree successfully using testfiles/TestKeepAlive.jmx
   [jmeter] WARNING: Could not open/create prefs root node 
Software\JavaSoft\Prefs at root 0x8002. Windows RegCreateKeyEx(...) 
returned error code 5.
   [jmeter] Starting the test @ Wed Jul 18 21:27:33 UTC 2018 (1531949253894)
   [jmeter] Waiting for possible Shutdown/StopTestNow/Heapdump message on port 
4445
   [jmeter] summary +  1 in 00:00:01 =1.5/s Avg:   617 Min:   617 Max:  
 617 Err: 0 (0.00%) Active: 1 Started: 1 Finished: 0
   [jmeter] summary +  7 in 00:01:02 =0.1/s Avg:   197 Min:   118 Max:  
 315 Err: 0 (0.00%) Active: 0 Started: 1 Finished: 1
   [jmeter] summary =  8 in 00:01:02 =0.1/s Avg:   250 Min:   118 Max:  
 617 Err: 0 (0.00%)
   [jmeter] Tidying up ...@ Wed Jul 18 21:28:37 UTC 2018 (1531949317468)
   [jmeter] ... end of run
 [echo] TestKeepAlive output files compared OK

batchtest:
 [echo] Starting ResponseDecompression with file ResponseDecompression.jmx 
using -X -Jdummy=dummy
   [jmeter] SLF4J: Class path contains multiple SLF4J bindings.
   [jmeter] SLF4J: Found binding in 
[jar:file:/F:/jenkins/jenkins-slave/workspace/JMeter%20Windows/trunk/lib/log4j-slf4j-impl-2.11.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
   [jmeter] SLF4J: Found binding in 
[jar:file:/F:/jenkins/jenkins-slave/workspace/JMeter%20Windows/trunk/lib/opt/activemq-all-5.15.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
   [jmeter] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
explanation.
   [jmeter] SLF4J: Actual binding is of type 
[org.apache.logging.slf4j.Log4jLoggerFactory]
   [jmeter] Creating summariser 
   [jmeter] Jul 18, 2018 9:28:40 PM java.util.prefs.WindowsPreferences 
Created the tree successfully using testfiles/ResponseDecompression.jmx
   [jmeter] WARNING: Could not open/create prefs root node 
Software\JavaSoft\Prefs at root 0x8002. Windows RegCreateKeyEx(...) 
returned error code 5.
   [jmeter] 
   [jmeter] Starting the test @ Wed Jul 18 21:28:40 UTC 2018 (1531949320118)
   [jmeter] Waiting for possible Shutdown/StopTestNow/Heapdump message on port 
4445
   [jmeter] summary =  6 in 00:00:03 =2.4/s Avg:   354 Min:   108 Max:  
 851 Err: 0 (0.00%)
   [jmeter] Tidying up ...@ Wed Jul 18 21:28:43 UTC 2018 (1531949323319)
   [jmeter] ... end of run
 [echo] ResponseDecompressio

Re: Bug 61805 - Allow simple HTTP request

2018-07-18 Thread Philippe Mouawad
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
   |--- HTTP Request with URL in path
  | -- Header Manager with User-Agent
set to ApacheJMeter
  | View Results Tree


What's your thoughts ?

Regards

On Wed, Dec 6, 2017 at 7:27 AM, Or Mark  wrote:

> I need your opinions about an enhancement I opened.
>
> I want to be able to execute Sampler (especially HTTP) on demand without
> execute full test.
>
> This can be done in postman or in blazemeter ( or calling cUrl ).
>
> I want to know what is the scope of the change can be. Beacause it can be
> very wide or/and specific,
>
> I'm suggesting adding a Send button in Sampler, but it can be on hierarchy
> tree or on right click on a Sampler.
>
> Easiest option is to send url as is inside path.
>
> Second option is to send all attributes of Sampler as is.
>
> Third option is to evaluate all variables and functions in Sampler which
> means to load variables and properties in Test plan/Thread group level.
>
> Thank you in advanced,
> Ori marko
>



-- 
Cordialement.
Philippe Mouawad.


buildbot failure in on jmeter-trunk

2018-07-18 Thread buildbot
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 scheduler named 'on-jmeter-commit' 
triggered this build
Build Source Stamp: [branch jmeter/trunk] 1836225
Blamelist: pmouawad

BUILD FAILED: failed shell_2 shell_3

Sincerely,
 -The Buildbot





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

2018-07-18 Thread Apache Jenkins Server
See 




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

2018-07-18 Thread sebb
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.

> It would makes things easier for us.
>
>
>>
>> If the originator does not respond, try making a dummy commit with the
>> appropriate 'this fixes #nnn' comment.
>
>
> Thanks, will do
>
>>
>> On 18 July 2018 at 15:41, pmouawad  wrote:
>> > 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
>> >
>> >
>> > ---
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.


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

2018-07-18 Thread Philippe Mouawad
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 dummy commit with the
> appropriate 'this fixes #nnn' comment.


Thanks, will do

>
> On 18 July 2018 at 15:41, pmouawad  wrote:
> > 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
> >
> >
> > ---
>


-- 
Cordialement.
Philippe Mouawad.


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

2018-07-18 Thread sebb
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 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
>
>
> ---


Re: Generating report by default in NON GUI mode

2018-07-18 Thread Philippe Mouawad
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 accurate ? :)

>
> Because when I made a big load test (many days with a high traffic), the
> generation of dashboard take a lot of time


You would force a non generation in this case no?



>
> Antonio
>
> Le dim. 15 juil. 2018 à 14:55, Philippe Mouawad <
> p.moua...@ubik-ingenierie.com> a écrit :
>
> > Hello,
> > Don't you think we should generate HTML report by default when running in
> > NON Gui mode ?
> >
> > I see 3 reasons for that:
> >
> >- Why would somebody in 80% of cases do a load test without this
> report
> >output ?
> >- Still now, I continue to read "dishonnest" comparisons of JMeter
> with
> >other tools (commercial or not) that say "JMeter has no reporting
> > feature":
> >   -
> > https://www.neotys.com/insights/how-neoload-is-different-from-jmeter
> >   - http://blog.loadimpact.com/how-to-do-10-things-in-jmeter-vs-k6
> >   - https://www.guru99.com/performance-testing-tools.html
> >   - https://www.loadtestingtool.com/wapt-vs-jmeter.shtml
> >   - When doing  trainings introducing JMeter, attendees are always
> >surprised this report is not generated by default
> >
> >
> > Globally, JMeter offers a lot of features but many must be activated
> which
> > is a bit sad, activating some would reduce learning curve and make it
> more
> > user friendly
> >
> > --
> > Regards.
> > Philippe
> >
>


-- 
Cordialement.
Philippe Mouawad.


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

2018-07-18 Thread Philippe Mouawad
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 default
> +1
>
> About  ignore View Results Tree on non GUI tests, I am not ok because
> sometime I use "Log/Display Only on Errors" to have a "screenshot on
> errors" to debug easily my script/dataset



Maybe this would be a special view results tree that is ignored in non gui
mode ?

>
> Antonio
>
>
> Le dim. 15 juil. 2018 à 15:27, Jmeter Tea  a écrit :
>
> > +1
> > But need to ignore View Results Tree (by default?) on non GUI tests
> > (Important best practice in not to use View Results Tree/Listeners in non
> > GUI)
> > Notice existing Issue 62495  Add option to disable View Results
> > Tree/Listeners in non GUI
> >
> > On Sun, Jul 15, 2018 at 4:04 PM, Philippe Mouawad <
> > p.moua...@ubik-ingenierie.com> wrote:
> >
> > > Hello,
> > > This has been opened as a bug and discussion was request, so putting it
> > > here:
> > >
> > > 
> > > 
> > >
> > > Today compared to other commercial load test tools, it may not be
> > > obvious to users how to:
> > > - Record
> > > - validate
> > > - Load Test
> > >
> > > This issue is to tackle the item and see what can be proposed.
> > >
> > >
> > > For example:
> > >
> > > - Maybe the recorder should be here by default and not deletable and a
> > > record button could then be added as a menu
> > > - Also, why not always have by default a View Results Tree that is
> > > used for Debugging a script
> > > - And finally, since a Thread Group is the mandatory component to add
> > > Test items, it should be here by default
> > >
> > >
> > > 
> > > 
> > >
> > > --
> > > Regards.
> > > Philippe Mouawad.
> > >
> >
>


-- 
Cordialement.
Philippe Mouawad.


Re: SubResult Naming Policy

2018-07-18 Thread Philippe Mouawad
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, 2018 at 4:10 PM, Philippe Mouawad <
> p.moua...@ubik-ingenierie.com> wrote:
>
>> Hello,
>> We would as a consequence to change property:
>>
>>
>>- jmeter.save.saveservice.url=true
>>
>> Regards
>>
>> On Tue, Jul 17, 2018 at 7:29 AM, Philippe Mouawad <
>> p.moua...@ubik-ingenierie.com> wrote:
>>
>>> Hello,
>>> With new version, subresults will also be available in CSV file.
>>> As a consequence they 'll be taken into account in dashboard:
>>>
>>>- Hits Per Second which excluded embedded resources can now include
>>>them
>>>
>>> But I think we need to make a modification on SubResults naming.
>>>
>>> Currently, they are named as per URL for HTTP Request for example.
>>> I suggest sub results follow naming policy so that they are correctly
>>> handled by Report.
>>>
>>> Thoughts ?
>>>
>>> Regards
>>> Philippe
>>>
>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>> Ubik-Ingénierie
>>
>> UBIK LOAD PACK Web Site 
>>
>> UBIK LOAD PACK on TWITTER 
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
> Ubik-Ingénierie
>
> UBIK LOAD PACK Web Site 
>
> UBIK LOAD PACK on TWITTER 
>
>

-- 
Cordialement.
Philippe Mouawad.
Ubik-Ingénierie

UBIK LOAD PACK Web Site 

UBIK LOAD PACK on TWITTER 


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

2018-07-18 Thread pmouawad
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

2018-07-18 Thread buildbot
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 scheduler named 'on-jmeter-commit' 
triggered this build
Build Source Stamp: [branch jmeter/trunk] 1836169
Blamelist: pmouawad

Build succeeded!

Sincerely,
 -The Buildbot