You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jmeter.apache.org by Milamber <mi...@apache.org> on 2016/11/02 21:14:16 UTC
Re: svn commit: r1767314 - /jmeter/trunk/xdocs/index.xml
> + <li><b><a href="usermanual/get-started.html#non_gui">CLI mode (NON GUI)</a></b> to load test from any Java compatible OS (Windows, Linux, Mac)</li>
I'm not sure that the CLI mode = Non GUI.
In my mind, the CLI mode is a command line mode to have interactive
actions with JMeter with command line (like bash in Linux, or wsadmin.sh
with WebSphere, or jboss-cli.sh with JBoss)
CLI means : command-line interface or command language interpreter (so
means that JMeter a CLI interperter ?)
https://en.wikipedia.org/wiki/Command-line_interface
On 31/10/2016 15:51, pmouawad@apache.org wrote:
> Author: pmouawad
> Date: Mon Oct 31 15:51:15 2016
> New Revision: 1767314
>
> URL: http://svn.apache.org/viewvc?rev=1767314&view=rev
> Log:
> Rework presentation
> Highlight features
>
> Modified:
> jmeter/trunk/xdocs/index.xml
>
> Modified: jmeter/trunk/xdocs/index.xml
> URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/index.xml?rev=1767314&r1=1767313&r2=1767314&view=diff
> ==============================================================================
> --- jmeter/trunk/xdocs/index.xml (original)
> +++ jmeter/trunk/xdocs/index.xml Mon Oct 31 15:51:15 2016
> @@ -34,20 +34,17 @@
> <h2>What can I do with it?</h2>
> <p>
> Apache JMeter may be used to test performance both on static and dynamic
> - resources (Webservices (SOAP/REST), Web dynamic languages - PHP, Java, ASP.NET, Files, etc. -, Java Objects, Data Bases and
> - Queries, FTP Servers and more). It can be used to simulate a heavy
> -load on a server, group of servers, network or object to test its strength or to analyze
> -overall performance under different load types. You can use it to make a
> -graphical analysis of performance or to test your server/script/object
> -behavior under heavy concurrent load.
> -</p>
> -<h2>What does it do?</h2>
> + resources , Web dynamic applications. <br/>
> + It can be used to simulate a heavy load on a server, group of servers,
> + network or object to test its strength or to analyze overall performance
> + under different load types.<br/>
> + </p>
> <p>Apache JMeter features include:</p>
> <ul>
> - <li>Ability to load and performance test many different server/protocol types:
> + <li>Ability to load and performance test many different applications/server/protocol types:
> <ul>
> - <li>Web - HTTP, HTTPS</li>
> - <li>SOAP / REST</li>
> + <li>Web - HTTP, HTTPS (Java, NodeJS, PHP, ASP.NET...)</li>
> + <li>SOAP / REST Webservices</li>
> <li>FTP</li>
> <li>Database via JDBC</li>
> <li>LDAP</li>
> @@ -55,12 +52,17 @@ behavior under heavy concurrent load.
> <li>Mail - SMTP(S), POP3(S) and IMAP(S)</li>
> <li>Native commands or shell scripts</li>
> <li>TCP</li>
> + <li>Java Objects</li>
> </ul>
> </li>
> + <li>Full featured Test IDE that allows faster Test Plan <b>recording, building and debugging</b>.</li>
> + <li><b><a href="usermanual/get-started.html#non_gui">CLI mode (NON GUI)</a></b> to load test from any Java compatible OS (Windows, Linux, Mac)</li>
> + <li>Analysis of Load Test thanks to a clear, complete and dynamic <b><a href="usermanual/generating-dashboard.html" >ready to present HTML report</a></b></li>
> + <li>Easy correlation for most popular formats, <b><a href="usermanual/component_reference.html#CSS/JQuery_Extractor" >HTML</a>, <a href="usermanual/component_reference.html#JSON_Extractor" >JSON </a>,
> + <a href="usermanual/component_reference.html#XPath_Extractor" >XML</a> or <a href="usermanual/component_reference.html#Regular_Expression_Extractor" >any textual format</a></b></li>
> <li>Complete portability and <b>100% Java purity</b>.</li>
> - <li>Full <b>multithreading</b> framework allows concurrent sampling by many threads and
> + <li>Full <b>multi-threading</b> framework allows concurrent sampling by many threads and
> simultaneous sampling of different functions by separate thread groups.</li>
> - <li>Careful <b>GUI</b> design allows faster Test Plan building and debugging.</li>
> <li>Caching and offline analysis/replaying of test results.</li>
> <li><b>Highly Extensible core:</b>
> <ul>
> @@ -69,20 +71,10 @@ behavior under heavy concurrent load.
> <li>Data analysis and <b>visualization plugins</b> allow great extensibility
> as well as personalization.</li>
> <li>Functions can be used to provide dynamic input to a test or provide data manipulation.</li>
> - <li><b>Scriptable Samplers</b> (BeanShell, BSF-compatible languages and JSR223-compatible languages)</li>
> + <li><b>Scriptable Samplers</b> (JSR223-compatible languages (<a href="http://groovy-lang.org">Groovy</a>) and BeanShell)</li>
> </ul>
> </li>
> </ul>
> -<h2>JMeter is not a browser</h2>
> -<p>
> -JMeter is not a browser.
> -As far as web-services and remote services are concerned, JMeter looks like a browser (or rather, multiple browsers);
> -however JMeter does not perform all the actions supported by browsers.
> -In particular, JMeter does not execute the Javascript found in HTML pages.
> -Nor does it render the HTML pages as a browser does
> -(it's possible to view the response as HTML etc., but the timings are not included in any samples, and only one sample in one thread is ever viewed at a time).
> -</p>
> -
> <h2>How do I do it?</h2>
> <ul>
> <li><a href="usermanual/index.html">Using JMeter</a> to understand how to use JMeter</li>
> @@ -94,6 +86,17 @@ Nor does it render the HTML pages as a b
> <li><a href="http://wiki.apache.org/jmeter/">JMeter Wiki</a></li>
> <li><a href="building.html">Building JMeter and Add-Ons</a> for advanced usage</li>
> </ul>
> +
> +<h2>JMeter is not a browser</h2>
> +<p>
> +JMeter is not a browser, it works at protocol level.
> +As far as web-services and remote services are concerned, JMeter looks like a browser (or rather, multiple browsers);
> +however JMeter does not perform all the actions supported by browsers.
> +In particular, JMeter does not execute the Javascript found in HTML pages.
> +Nor does it render the HTML pages as a browser does
> +(it's possible to view the response as HTML etc., but the timings are not included in any samples, and only one sample in one thread is ever viewed at a time).
> +</p>
> +
> <h2>Tutorials (PDF)</h2>
> <ul>
> <li><a href="usermanual/jmeter_distributed_testing_step_by_step.pdf">Distributed Testing</a></li>
>
>
>
Re: svn commit: r1767314 - /jmeter/trunk/xdocs/index.xml
Posted by sebb <se...@gmail.com>.
On 2 November 2016 at 21:27, Philippe Mouawad
<ph...@gmail.com> wrote:
> For me, Non gui has no meaning for newbies .
> I think cli is ok and understandable ,
+1
Maybe spell it out as command-line (interface)?
But I favour adding (non-GUI) where necessary to make it double clear.
> since afaik we use an avalon version
It was derived from Avalon but is built-in to JMeter
> of cli that we should probably migrate one day to commons-cli from apache.
-1
I did look at switching to Commons-CLI a long time ago and there were
lots of issues with it.
Migrating would likely change the argument syntax, and cause subtle
problems for existing scripts.
AFAICR there have been only one or two bugs/enhancements related to
the JMeter command-line parser in the last 10+ years and they were
quickly solved.
I see no advantages, and plenty of disadvantages.
> I still see (on twitter, stackoverflow, private mails) a lot of newbies and
> even users not being aware of the non gui mode and I think it's due to the
> name. Clo is more meaningful.
>
> We must make it clear that cli is for load testing, gui for
> building/debugging.
>
> Regards
>
> On Wednesday, November 2, 2016, Milamber <mi...@apache.org> wrote:
>
>>
>> + <li><b><a href="usermanual/get-started.html#non_gui">CLI mode (NON
>>> GUI)</a></b> to load test from any Java compatible OS (Windows, Linux,
>>> Mac)</li>
>>>
>>
>>
>> I'm not sure that the CLI mode = Non GUI.
>> In my mind, the CLI mode is a command line mode to have interactive
>> actions with JMeter with command line (like bash in Linux, or wsadmin.sh
>> with WebSphere, or jboss-cli.sh with JBoss)
>>
>> CLI means : command-line interface or command language interpreter (so
>> means that JMeter a CLI interperter ?)
>>
>> https://en.wikipedia.org/wiki/Command-line_interface
>>
>>
>>
>>
>> On 31/10/2016 15:51, pmouawad@apache.org wrote:
>>
>>> Author: pmouawad
>>> Date: Mon Oct 31 15:51:15 2016
>>> New Revision: 1767314
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1767314&view=rev
>>> Log:
>>> Rework presentation
>>> Highlight features
>>>
>>> Modified:
>>> jmeter/trunk/xdocs/index.xml
>>>
>>> Modified: jmeter/trunk/xdocs/index.xml
>>> URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/index.xml?re
>>> v=1767314&r1=1767313&r2=1767314&view=diff
>>> ============================================================
>>> ==================
>>> --- jmeter/trunk/xdocs/index.xml (original)
>>> +++ jmeter/trunk/xdocs/index.xml Mon Oct 31 15:51:15 2016
>>> @@ -34,20 +34,17 @@
>>> <h2>What can I do with it?</h2>
>>> <p>
>>> Apache JMeter may be used to test performance both on static and
>>> dynamic
>>> - resources (Webservices (SOAP/REST), Web dynamic languages - PHP,
>>> Java, ASP.NET, Files, etc. -, Java Objects, Data Bases and
>>> - Queries, FTP Servers and more). It can be used to simulate a heavy
>>> -load on a server, group of servers, network or object to test its
>>> strength or to analyze
>>> -overall performance under different load types. You can use it to make a
>>> -graphical analysis of performance or to test your server/script/object
>>> -behavior under heavy concurrent load.
>>> -</p>
>>> -<h2>What does it do?</h2>
>>> + resources , Web dynamic applications. <br/>
>>> + It can be used to simulate a heavy load on a server, group of
>>> servers,
>>> + network or object to test its strength or to analyze overall
>>> performance
>>> + under different load types.<br/>
>>> + </p>
>>> <p>Apache JMeter features include:</p>
>>> <ul>
>>> - <li>Ability to load and performance test many different
>>> server/protocol types:
>>> + <li>Ability to load and performance test many different
>>> applications/server/protocol types:
>>> <ul>
>>> - <li>Web - HTTP, HTTPS</li>
>>> - <li>SOAP / REST</li>
>>> + <li>Web - HTTP, HTTPS (Java, NodeJS, PHP, ASP.NET...)</li>
>>> + <li>SOAP / REST Webservices</li>
>>> <li>FTP</li>
>>> <li>Database via JDBC</li>
>>> <li>LDAP</li>
>>> @@ -55,12 +52,17 @@ behavior under heavy concurrent load.
>>> <li>Mail - SMTP(S), POP3(S) and IMAP(S)</li>
>>> <li>Native commands or shell scripts</li>
>>> <li>TCP</li>
>>> + <li>Java Objects</li>
>>> </ul>
>>> </li>
>>> + <li>Full featured Test IDE that allows faster Test Plan
>>> <b>recording, building and debugging</b>.</li>
>>> + <li><b><a href="usermanual/get-started.html#non_gui">CLI mode (NON
>>> GUI)</a></b> to load test from any Java compatible OS (Windows, Linux,
>>> Mac)</li>
>>> + <li>Analysis of Load Test thanks to a clear, complete and dynamic
>>> <b><a href="usermanual/generating-dashboard.html" >ready to present HTML
>>> report</a></b></li>
>>> + <li>Easy correlation for most popular formats, <b><a
>>> href="usermanual/component_reference.html#CSS/JQuery_Extractor"
>>> >HTML</a>, <a href="usermanual/component_reference.html#JSON_Extractor"
>>> >JSON </a>,
>>> + <a href="usermanual/component_reference.html#XPath_Extractor"
>>> >XML</a> or <a href="usermanual/component_ref
>>> erence.html#Regular_Expression_Extractor" >any textual
>>> format</a></b></li>
>>> <li>Complete portability and <b>100% Java purity</b>.</li>
>>> - <li>Full <b>multithreading</b> framework allows concurrent sampling
>>> by many threads and
>>> + <li>Full <b>multi-threading</b> framework allows concurrent sampling
>>> by many threads and
>>> simultaneous sampling of different functions by separate thread
>>> groups.</li>
>>> - <li>Careful <b>GUI</b> design allows faster Test Plan building and
>>> debugging.</li>
>>> <li>Caching and offline analysis/replaying of test results.</li>
>>> <li><b>Highly Extensible core:</b>
>>> <ul>
>>> @@ -69,20 +71,10 @@ behavior under heavy concurrent load.
>>> <li>Data analysis and <b>visualization plugins</b> allow great
>>> extensibility
>>> as well as personalization.</li>
>>> <li>Functions can be used to provide dynamic input to a test or
>>> provide data manipulation.</li>
>>> - <li><b>Scriptable Samplers</b> (BeanShell, BSF-compatible
>>> languages and JSR223-compatible languages)</li>
>>> + <li><b>Scriptable Samplers</b> (JSR223-compatible languages (<a
>>> href="http://groovy-lang.org">Groovy</a>) and BeanShell)</li>
>>> </ul>
>>> </li>
>>> </ul>
>>> -<h2>JMeter is not a browser</h2>
>>> -<p>
>>> -JMeter is not a browser.
>>> -As far as web-services and remote services are concerned, JMeter looks
>>> like a browser (or rather, multiple browsers);
>>> -however JMeter does not perform all the actions supported by browsers.
>>> -In particular, JMeter does not execute the Javascript found in HTML
>>> pages.
>>> -Nor does it render the HTML pages as a browser does
>>> -(it's possible to view the response as HTML etc., but the timings are
>>> not included in any samples, and only one sample in one thread is ever
>>> viewed at a time).
>>> -</p>
>>> -
>>> <h2>How do I do it?</h2>
>>> <ul>
>>> <li><a href="usermanual/index.html">Using JMeter</a> to understand how
>>> to use JMeter</li>
>>> @@ -94,6 +86,17 @@ Nor does it render the HTML pages as a b
>>> <li><a href="http://wiki.apache.org/jmeter/">JMeter Wiki</a></li>
>>> <li><a href="building.html">Building JMeter and Add-Ons</a> for
>>> advanced usage</li>
>>> </ul>
>>> +
>>> +<h2>JMeter is not a browser</h2>
>>> +<p>
>>> +JMeter is not a browser, it works at protocol level.
>>> +As far as web-services and remote services are concerned, JMeter looks
>>> like a browser (or rather, multiple browsers);
>>> +however JMeter does not perform all the actions supported by browsers.
>>> +In particular, JMeter does not execute the Javascript found in HTML
>>> pages.
>>> +Nor does it render the HTML pages as a browser does
>>> +(it's possible to view the response as HTML etc., but the timings are
>>> not included in any samples, and only one sample in one thread is ever
>>> viewed at a time).
>>> +</p>
>>> +
>>> <h2>Tutorials (PDF)</h2>
>>> <ul>
>>> <li><a href="usermanual/jmeter_distributed_testing_step_by_step.pdf">Distributed
>>> Testing</a></li>
>>>
>>>
>>>
>>>
>>
>
> --
> Cordialement.
> Philippe Mouawad.
Re: svn commit: r1767314 - /jmeter/trunk/xdocs/index.xml
Posted by sebb <se...@gmail.com>.
On 3 November 2016 at 11:42, Milamber <mi...@apache.org> wrote:
>
> I agree that Non-GUI isn't the good words to say "launch JMeter without
> graphical interface"
>
> But the "CLI mode" (cli + mode) isn't too the good words to say "launch
> JMeter without graphical interface and for heavy load tests"
>
> Perhaps change the "CLI Mode" to "Headless mode" (seems to be the good word)
>
> https://en.wikipedia.org/wiki/Headless_software
>
I think that's even less well known.
As I wrote, I think the problem here is using the acronym CLI.
command-line mode
or perhaps
console mode
Whatever is chosen, the Glossary needs to explain the terms GUI, CLI etc.
And the different modes should be explained early in the introduction.
>
>
> On 02/11/2016 21:27, Philippe Mouawad wrote:
>>
>> For me, Non gui has no meaning for newbies .
>> I think cli is ok and understandable , since afaik we use an avalon
>> version
>> of cli that we should probably migrate one day to commons-cli from apache.
>>
>> I still see (on twitter, stackoverflow, private mails) a lot of newbies
>> and
>> even users not being aware of the non gui mode and I think it's due to the
>> name. Clo is more meaningful.
>>
>> We must make it clear that cli is for load testing, gui for
>> building/debugging.
>>
>> Regards
>>
>> On Wednesday, November 2, 2016, Milamber <mi...@apache.org> wrote:
>>
>>> + <li><b><a href="usermanual/get-started.html#non_gui">CLI mode (NON
>>>>
>>>> GUI)</a></b> to load test from any Java compatible OS (Windows, Linux,
>>>> Mac)</li>
>>>>
>>>
>>> I'm not sure that the CLI mode = Non GUI.
>>> In my mind, the CLI mode is a command line mode to have interactive
>>> actions with JMeter with command line (like bash in Linux, or wsadmin.sh
>>> with WebSphere, or jboss-cli.sh with JBoss)
>>>
>>> CLI means : command-line interface or command language interpreter (so
>>> means that JMeter a CLI interperter ?)
>>>
>>> https://en.wikipedia.org/wiki/Command-line_interface
>>>
>>>
>>>
>>>
>>> On 31/10/2016 15:51, pmouawad@apache.org wrote:
>>>
>>>> Author: pmouawad
>>>> Date: Mon Oct 31 15:51:15 2016
>>>> New Revision: 1767314
>>>>
>>>> URL: http://svn.apache.org/viewvc?rev=1767314&view=rev
>>>> Log:
>>>> Rework presentation
>>>> Highlight features
>>>>
>>>> Modified:
>>>> jmeter/trunk/xdocs/index.xml
>>>>
>>>> Modified: jmeter/trunk/xdocs/index.xml
>>>> URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/index.xml?re
>>>> v=1767314&r1=1767313&r2=1767314&view=diff
>>>> ============================================================
>>>> ==================
>>>> --- jmeter/trunk/xdocs/index.xml (original)
>>>> +++ jmeter/trunk/xdocs/index.xml Mon Oct 31 15:51:15 2016
>>>> @@ -34,20 +34,17 @@
>>>> <h2>What can I do with it?</h2>
>>>> <p>
>>>> Apache JMeter may be used to test performance both on static
>>>> and
>>>> dynamic
>>>> - resources (Webservices (SOAP/REST), Web dynamic languages - PHP,
>>>> Java, ASP.NET, Files, etc. -, Java Objects, Data Bases and
>>>> - Queries, FTP Servers and more). It can be used to simulate a
>>>> heavy
>>>> -load on a server, group of servers, network or object to test its
>>>> strength or to analyze
>>>> -overall performance under different load types. You can use it to make
>>>> a
>>>> -graphical analysis of performance or to test your server/script/object
>>>> -behavior under heavy concurrent load.
>>>> -</p>
>>>> -<h2>What does it do?</h2>
>>>> + resources , Web dynamic applications. <br/>
>>>> + It can be used to simulate a heavy load on a server, group of
>>>> servers,
>>>> + network or object to test its strength or to analyze overall
>>>> performance
>>>> + under different load types.<br/>
>>>> + </p>
>>>> <p>Apache JMeter features include:</p>
>>>> <ul>
>>>> - <li>Ability to load and performance test many different
>>>> server/protocol types:
>>>> + <li>Ability to load and performance test many different
>>>> applications/server/protocol types:
>>>> <ul>
>>>> - <li>Web - HTTP, HTTPS</li>
>>>> - <li>SOAP / REST</li>
>>>> + <li>Web - HTTP, HTTPS (Java, NodeJS, PHP, ASP.NET...)</li>
>>>> + <li>SOAP / REST Webservices</li>
>>>> <li>FTP</li>
>>>> <li>Database via JDBC</li>
>>>> <li>LDAP</li>
>>>> @@ -55,12 +52,17 @@ behavior under heavy concurrent load.
>>>> <li>Mail - SMTP(S), POP3(S) and IMAP(S)</li>
>>>> <li>Native commands or shell scripts</li>
>>>> <li>TCP</li>
>>>> + <li>Java Objects</li>
>>>> </ul>
>>>> </li>
>>>> + <li>Full featured Test IDE that allows faster Test Plan
>>>> <b>recording, building and debugging</b>.</li>
>>>> + <li><b><a href="usermanual/get-started.html#non_gui">CLI mode (NON
>>>> GUI)</a></b> to load test from any Java compatible OS (Windows, Linux,
>>>> Mac)</li>
>>>> + <li>Analysis of Load Test thanks to a clear, complete and dynamic
>>>> <b><a href="usermanual/generating-dashboard.html" >ready to present HTML
>>>> report</a></b></li>
>>>> + <li>Easy correlation for most popular formats, <b><a
>>>> href="usermanual/component_reference.html#CSS/JQuery_Extractor"
>>>>>
>>>>> HTML</a>, <a href="usermanual/component_reference.html#JSON_Extractor"
>>>>> JSON </a>,
>>>>
>>>> + <a href="usermanual/component_reference.html#XPath_Extractor"
>>>>>
>>>>> XML</a> or <a href="usermanual/component_ref
>>>>
>>>> erence.html#Regular_Expression_Extractor" >any textual
>>>> format</a></b></li>
>>>> <li>Complete portability and <b>100% Java purity</b>.</li>
>>>> - <li>Full <b>multithreading</b> framework allows concurrent sampling
>>>> by many threads and
>>>> + <li>Full <b>multi-threading</b> framework allows concurrent
>>>> sampling
>>>> by many threads and
>>>> simultaneous sampling of different functions by separate
>>>> thread
>>>> groups.</li>
>>>> - <li>Careful <b>GUI</b> design allows faster Test Plan building and
>>>> debugging.</li>
>>>> <li>Caching and offline analysis/replaying of test results.</li>
>>>> <li><b>Highly Extensible core:</b>
>>>> <ul>
>>>> @@ -69,20 +71,10 @@ behavior under heavy concurrent load.
>>>> <li>Data analysis and <b>visualization plugins</b> allow
>>>> great
>>>> extensibility
>>>> as well as personalization.</li>
>>>> <li>Functions can be used to provide dynamic input to a test
>>>> or
>>>> provide data manipulation.</li>
>>>> - <li><b>Scriptable Samplers</b> (BeanShell, BSF-compatible
>>>> languages and JSR223-compatible languages)</li>
>>>> + <li><b>Scriptable Samplers</b> (JSR223-compatible languages (<a
>>>> href="http://groovy-lang.org">Groovy</a>) and BeanShell)</li>
>>>> </ul>
>>>> </li>
>>>> </ul>
>>>> -<h2>JMeter is not a browser</h2>
>>>> -<p>
>>>> -JMeter is not a browser.
>>>> -As far as web-services and remote services are concerned, JMeter looks
>>>> like a browser (or rather, multiple browsers);
>>>> -however JMeter does not perform all the actions supported by browsers.
>>>> -In particular, JMeter does not execute the Javascript found in HTML
>>>> pages.
>>>> -Nor does it render the HTML pages as a browser does
>>>> -(it's possible to view the response as HTML etc., but the timings are
>>>> not included in any samples, and only one sample in one thread is ever
>>>> viewed at a time).
>>>> -</p>
>>>> -
>>>> <h2>How do I do it?</h2>
>>>> <ul>
>>>> <li><a href="usermanual/index.html">Using JMeter</a> to understand
>>>> how
>>>> to use JMeter</li>
>>>> @@ -94,6 +86,17 @@ Nor does it render the HTML pages as a b
>>>> <li><a href="http://wiki.apache.org/jmeter/">JMeter Wiki</a></li>
>>>> <li><a href="building.html">Building JMeter and Add-Ons</a> for
>>>> advanced usage</li>
>>>> </ul>
>>>> +
>>>> +<h2>JMeter is not a browser</h2>
>>>> +<p>
>>>> +JMeter is not a browser, it works at protocol level.
>>>> +As far as web-services and remote services are concerned, JMeter looks
>>>> like a browser (or rather, multiple browsers);
>>>> +however JMeter does not perform all the actions supported by browsers.
>>>> +In particular, JMeter does not execute the Javascript found in HTML
>>>> pages.
>>>> +Nor does it render the HTML pages as a browser does
>>>> +(it's possible to view the response as HTML etc., but the timings are
>>>> not included in any samples, and only one sample in one thread is ever
>>>> viewed at a time).
>>>> +</p>
>>>> +
>>>> <h2>Tutorials (PDF)</h2>
>>>> <ul>
>>>> <li><a
>>>> href="usermanual/jmeter_distributed_testing_step_by_step.pdf">Distributed
>>>> Testing</a></li>
>>>>
>>>>
>>>>
>>>>
>
Re: svn commit: r1767314 - /jmeter/trunk/xdocs/index.xml
Posted by Stuart Barlow <st...@gmail.com>.
IMHO Headless mode makes sense. It's commonly used with other software
already. Selenium for example.
CLI is a very old term and implies something slightly different. You
would launch an application from a command prompt or shell and interact
with it using text and commands. That is a CLI. With JMeter the user
just launches the application. They don't actively interact with an
interface afterwards (correct me if I'm wrong).
On 03.11.2016 13:06, Philippe Mouawad wrote:
> On Thursday, November 3, 2016, Milamber <mi...@apache.org> wrote:
>
>>
>> I agree that Non-GUI isn't the good words to say "launch JMeter
>> without
>> graphical interface"
>>
>> But the "CLI mode" (cli + mode) isn't too the good words to say
>> "launch
>> JMeter without graphical interface and for heavy load tests"
>>
>> Perhaps change the "CLI Mode" to "Headless mode" (seems to be the
>> good
>> word)
>>
>> https://en.wikipedia.org/wiki/Headless_software
>
> -1 for me . It's not clear.
>
> i prefer cli also for marketing reasons also.
>
>
>>
>>
>> On 02/11/2016 21:27, Philippe Mouawad wrote:
>>
>>> For me, Non gui has no meaning for newbies .
>>> I think cli is ok and understandable , since afaik we use an avalon
>>> version
>>> of cli that we should probably migrate one day to commons-cli from
>>> apache.
>>>
>>> I still see (on twitter, stackoverflow, private mails) a lot of
>>> newbies
>>> and
>>> even users not being aware of the non gui mode and I think it's due
>>> to the
>>> name. Clo is more meaningful.
>>>
>>> We must make it clear that cli is for load testing, gui for
>>> building/debugging.
>>>
>>> Regards
>>>
>>> On Wednesday, November 2, 2016, Milamber <mi...@apache.org>
>>> wrote:
>>>
>>> + <li><b><a href="usermanual/get-started.html#non_gui">CLI mode
>>> (NON
>>>>
>>>>> GUI)</a></b> to load test from any Java compatible OS (Windows,
>>>>> Linux,
>>>>> Mac)</li>
>>>>>
>>>>>
>>>> I'm not sure that the CLI mode = Non GUI.
>>>> In my mind, the CLI mode is a command line mode to have
>>>> interactive
>>>> actions with JMeter with command line (like bash in Linux, or
>>>> wsadmin.sh
>>>> with WebSphere, or jboss-cli.sh with JBoss)
>>>>
>>>> CLI means : command-line interface or command language interpreter
>>>> (so
>>>> means that JMeter a CLI interperter ?)
>>>>
>>>> https://en.wikipedia.org/wiki/Command-line_interface
>>>>
>>>>
>>>>
>>>>
>>>> On 31/10/2016 15:51, pmouawad@apache.org wrote:
>>>>
>>>> Author: pmouawad
>>>>> Date: Mon Oct 31 15:51:15 2016
>>>>> New Revision: 1767314
>>>>>
>>>>> URL: http://svn.apache.org/viewvc?rev=1767314&view=rev
>>>>> Log:
>>>>> Rework presentation
>>>>> Highlight features
>>>>>
>>>>> Modified:
>>>>> jmeter/trunk/xdocs/index.xml
>>>>>
>>>>> Modified: jmeter/trunk/xdocs/index.xml
>>>>> URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/index.xml?re
>>>>> v=1767314&r1=1767313&r2=1767314&view=diff
>>>>> ============================================================
>>>>> ==================
>>>>> --- jmeter/trunk/xdocs/index.xml (original)
>>>>> +++ jmeter/trunk/xdocs/index.xml Mon Oct 31 15:51:15 2016
>>>>> @@ -34,20 +34,17 @@
>>>>> <h2>What can I do with it?</h2>
>>>>> <p>
>>>>> Apache JMeter may be used to test performance both on
>>>>> static
>>>>> and
>>>>> dynamic
>>>>> - resources (Webservices (SOAP/REST), Web dynamic languages
>>>>> - PHP,
>>>>> Java, ASP.NET, Files, etc. -, Java Objects, Data Bases and
>>>>> - Queries, FTP Servers and more). It can be used to simulate
>>>>> a
>>>>> heavy
>>>>> -load on a server, group of servers, network or object to test
>>>>> its
>>>>> strength or to analyze
>>>>> -overall performance under different load types. You can use it
>>>>> to make
>>>>> a
>>>>> -graphical analysis of performance or to test your
>>>>> server/script/object
>>>>> -behavior under heavy concurrent load.
>>>>> -</p>
>>>>> -<h2>What does it do?</h2>
>>>>> + resources , Web dynamic applications. <br/>
>>>>> + It can be used to simulate a heavy load on a server, group
>>>>> of
>>>>> servers,
>>>>> + network or object to test its strength or to analyze
>>>>> overall
>>>>> performance
>>>>> + under different load types.<br/>
>>>>> + </p>
>>>>> <p>Apache JMeter features include:</p>
>>>>> <ul>
>>>>> - <li>Ability to load and performance test many different
>>>>> server/protocol types:
>>>>> + <li>Ability to load and performance test many different
>>>>> applications/server/protocol types:
>>>>> <ul>
>>>>> - <li>Web - HTTP, HTTPS</li>
>>>>> - <li>SOAP / REST</li>
>>>>> + <li>Web - HTTP, HTTPS (Java, NodeJS, PHP,
>>>>> ASP.NET...)</li>
>>>>> + <li>SOAP / REST Webservices</li>
>>>>> <li>FTP</li>
>>>>> <li>Database via JDBC</li>
>>>>> <li>LDAP</li>
>>>>> @@ -55,12 +52,17 @@ behavior under heavy concurrent load.
>>>>> <li>Mail - SMTP(S), POP3(S) and IMAP(S)</li>
>>>>> <li>Native commands or shell scripts</li>
>>>>> <li>TCP</li>
>>>>> + <li>Java Objects</li>
>>>>> </ul>
>>>>> </li>
>>>>> + <li>Full featured Test IDE that allows faster Test Plan
>>>>> <b>recording, building and debugging</b>.</li>
>>>>> + <li><b><a href="usermanual/get-started.html#non_gui">CLI
>>>>> mode (NON
>>>>> GUI)</a></b> to load test from any Java compatible OS (Windows,
>>>>> Linux,
>>>>> Mac)</li>
>>>>> + <li>Analysis of Load Test thanks to a clear, complete and
>>>>> dynamic
>>>>> <b><a href="usermanual/generating-dashboard.html" >ready to
>>>>> present
>>>>> HTML
>>>>> report</a></b></li>
>>>>> + <li>Easy correlation for most popular formats, <b><a
>>>>> href="usermanual/component_reference.html#CSS/JQuery_Extractor"
>>>>>
>>>>>> HTML</a>, <a
>>>>>> href="usermanual/component_reference.html#JSON_Extractor"
>>>>>> JSON </a>,
>>>>>>
>>>>> + <a
>>>>> href="usermanual/component_reference.html#XPath_Extractor"
>>>>>
>>>>>> XML</a> or <a href="usermanual/component_ref
>>>>>>
>>>>> erence.html#Regular_Expression_Extractor" >any textual
>>>>> format</a></b></li>
>>>>> <li>Complete portability and <b>100% Java purity</b>.</li>
>>>>> - <li>Full <b>multithreading</b> framework allows concurrent
>>>>> sampling
>>>>> by many threads and
>>>>> + <li>Full <b>multi-threading</b> framework allows concurrent
>>>>> sampling
>>>>> by many threads and
>>>>> simultaneous sampling of different functions by
>>>>> separate
>>>>> thread
>>>>> groups.</li>
>>>>> - <li>Careful <b>GUI</b> design allows faster Test Plan
>>>>> building and
>>>>> debugging.</li>
>>>>> <li>Caching and offline analysis/replaying of test
>>>>> results.</li>
>>>>> <li><b>Highly Extensible core:</b>
>>>>> <ul>
>>>>> @@ -69,20 +71,10 @@ behavior under heavy concurrent load.
>>>>> <li>Data analysis and <b>visualization plugins</b>
>>>>> allow
>>>>> great
>>>>> extensibility
>>>>> as well as personalization.</li>
>>>>> <li>Functions can be used to provide dynamic input to
>>>>> a test
>>>>> or
>>>>> provide data manipulation.</li>
>>>>> - <li><b>Scriptable Samplers</b> (BeanShell,
>>>>> BSF-compatible
>>>>> languages and JSR223-compatible languages)</li>
>>>>> + <li><b>Scriptable Samplers</b> (JSR223-compatible
>>>>> languages (<a
>>>>> href="http://groovy-lang.org">Groovy</a>) and BeanShell)</li>
>>>>> </ul>
>>>>> </li>
>>>>> </ul>
>>>>> -<h2>JMeter is not a browser</h2>
>>>>> -<p>
>>>>> -JMeter is not a browser.
>>>>> -As far as web-services and remote services are concerned, JMeter
>>>>> looks
>>>>> like a browser (or rather, multiple browsers);
>>>>> -however JMeter does not perform all the actions supported by
>>>>> browsers.
>>>>> -In particular, JMeter does not execute the Javascript found in
>>>>> HTML
>>>>> pages.
>>>>> -Nor does it render the HTML pages as a browser does
>>>>> -(it's possible to view the response as HTML etc., but the
>>>>> timings are
>>>>> not included in any samples, and only one sample in one thread is
>>>>> ever
>>>>> viewed at a time).
>>>>> -</p>
>>>>> -
>>>>> <h2>How do I do it?</h2>
>>>>> <ul>
>>>>> <li><a href="usermanual/index.html">Using JMeter</a> to
>>>>> understand
>>>>> how
>>>>> to use JMeter</li>
>>>>> @@ -94,6 +86,17 @@ Nor does it render the HTML pages as a b
>>>>> <li><a href="http://wiki.apache.org/jmeter/">JMeter
>>>>> Wiki</a></li>
>>>>> <li><a href="building.html">Building JMeter and Add-Ons</a>
>>>>> for
>>>>> advanced usage</li>
>>>>> </ul>
>>>>> +
>>>>> +<h2>JMeter is not a browser</h2>
>>>>> +<p>
>>>>> +JMeter is not a browser, it works at protocol level.
>>>>> +As far as web-services and remote services are concerned, JMeter
>>>>> looks
>>>>> like a browser (or rather, multiple browsers);
>>>>> +however JMeter does not perform all the actions supported by
>>>>> browsers.
>>>>> +In particular, JMeter does not execute the Javascript found in
>>>>> HTML
>>>>> pages.
>>>>> +Nor does it render the HTML pages as a browser does
>>>>> +(it's possible to view the response as HTML etc., but the
>>>>> timings are
>>>>> not included in any samples, and only one sample in one thread is
>>>>> ever
>>>>> viewed at a time).
>>>>> +</p>
>>>>> +
>>>>> <h2>Tutorials (PDF)</h2>
>>>>> <ul>
>>>>> <li><a
>>>>> href="usermanual/jmeter_distributed_testing_step_by_step.
>>>>> pdf">Distributed
>>>>> Testing</a></li>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>
Re: svn commit: r1767314 - /jmeter/trunk/xdocs/index.xml
Posted by Philippe Mouawad <ph...@gmail.com>.
On Friday, November 4, 2016, Milamber <mi...@apache.org> wrote:
>
>
> On 03/11/2016 12:06, Philippe Mouawad wrote:
>
>> On Thursday, November 3, 2016, Milamber <mi...@apache.org> wrote:
>>
>> I agree that Non-GUI isn't the good words to say "launch JMeter without
>>> graphical interface"
>>>
>>> But the "CLI mode" (cli + mode) isn't too the good words to say "launch
>>> JMeter without graphical interface and for heavy load tests"
>>>
>>> Perhaps change the "CLI Mode" to "Headless mode" (seems to be the good
>>> word)
>>>
>>> https://en.wikipedia.org/wiki/Headless_software
>>>
>> -1 for me . It's not clear.
>>
>> i prefer cli also for marketing reasons also.
>>
>
>
> "command-line mode" ? sound good for you ?
Whatever you like.
If headless is used and more Meaningful then why not.
Let's not block release process for that.
>
>
>
>>
>>
>>> On 02/11/2016 21:27, Philippe Mouawad wrote:
>>>
>>> For me, Non gui has no meaning for newbies .
>>>> I think cli is ok and understandable , since afaik we use an avalon
>>>> version
>>>> of cli that we should probably migrate one day to commons-cli from
>>>> apache.
>>>>
>>>> I still see (on twitter, stackoverflow, private mails) a lot of newbies
>>>> and
>>>> even users not being aware of the non gui mode and I think it's due to
>>>> the
>>>> name. Clo is more meaningful.
>>>>
>>>> We must make it clear that cli is for load testing, gui for
>>>> building/debugging.
>>>>
>>>> Regards
>>>>
>>>> On Wednesday, November 2, 2016, Milamber <mi...@apache.org> wrote:
>>>>
>>>> + <li><b><a href="usermanual/get-started.html#non_gui">CLI mode (NON
>>>>
>>>>> GUI)</a></b> to load test from any Java compatible OS (Windows, Linux,
>>>>>> Mac)</li>
>>>>>>
>>>>>>
>>>>>> I'm not sure that the CLI mode = Non GUI.
>>>>> In my mind, the CLI mode is a command line mode to have interactive
>>>>> actions with JMeter with command line (like bash in Linux, or
>>>>> wsadmin.sh
>>>>> with WebSphere, or jboss-cli.sh with JBoss)
>>>>>
>>>>> CLI means : command-line interface or command language interpreter (so
>>>>> means that JMeter a CLI interperter ?)
>>>>>
>>>>> https://en.wikipedia.org/wiki/Command-line_interface
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 31/10/2016 15:51, pmouawad@apache.org wrote:
>>>>>
>>>>> Author: pmouawad
>>>>>
>>>>>> Date: Mon Oct 31 15:51:15 2016
>>>>>> New Revision: 1767314
>>>>>>
>>>>>> URL: http://svn.apache.org/viewvc?rev=1767314&view=rev
>>>>>> Log:
>>>>>> Rework presentation
>>>>>> Highlight features
>>>>>>
>>>>>> Modified:
>>>>>> jmeter/trunk/xdocs/index.xml
>>>>>>
>>>>>> Modified: jmeter/trunk/xdocs/index.xml
>>>>>> URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/index.xml?re
>>>>>> v=1767314&r1=1767313&r2=1767314&view=diff
>>>>>> ============================================================
>>>>>> ==================
>>>>>> --- jmeter/trunk/xdocs/index.xml (original)
>>>>>> +++ jmeter/trunk/xdocs/index.xml Mon Oct 31 15:51:15 2016
>>>>>> @@ -34,20 +34,17 @@
>>>>>> <h2>What can I do with it?</h2>
>>>>>> <p>
>>>>>> Apache JMeter may be used to test performance both on static
>>>>>> and
>>>>>> dynamic
>>>>>> - resources (Webservices (SOAP/REST), Web dynamic languages -
>>>>>> PHP,
>>>>>> Java, ASP.NET, Files, etc. -, Java Objects, Data Bases and
>>>>>> - Queries, FTP Servers and more). It can be used to simulate a
>>>>>> heavy
>>>>>> -load on a server, group of servers, network or object to test its
>>>>>> strength or to analyze
>>>>>> -overall performance under different load types. You can use it to
>>>>>> make
>>>>>> a
>>>>>> -graphical analysis of performance or to test your
>>>>>> server/script/object
>>>>>> -behavior under heavy concurrent load.
>>>>>> -</p>
>>>>>> -<h2>What does it do?</h2>
>>>>>> + resources , Web dynamic applications. <br/>
>>>>>> + It can be used to simulate a heavy load on a server, group of
>>>>>> servers,
>>>>>> + network or object to test its strength or to analyze overall
>>>>>> performance
>>>>>> + under different load types.<br/>
>>>>>> + </p>
>>>>>> <p>Apache JMeter features include:</p>
>>>>>> <ul>
>>>>>> - <li>Ability to load and performance test many different
>>>>>> server/protocol types:
>>>>>> + <li>Ability to load and performance test many different
>>>>>> applications/server/protocol types:
>>>>>> <ul>
>>>>>> - <li>Web - HTTP, HTTPS</li>
>>>>>> - <li>SOAP / REST</li>
>>>>>> + <li>Web - HTTP, HTTPS (Java, NodeJS, PHP, ASP.NET...)</li>
>>>>>> + <li>SOAP / REST Webservices</li>
>>>>>> <li>FTP</li>
>>>>>> <li>Database via JDBC</li>
>>>>>> <li>LDAP</li>
>>>>>> @@ -55,12 +52,17 @@ behavior under heavy concurrent load.
>>>>>> <li>Mail - SMTP(S), POP3(S) and IMAP(S)</li>
>>>>>> <li>Native commands or shell scripts</li>
>>>>>> <li>TCP</li>
>>>>>> + <li>Java Objects</li>
>>>>>> </ul>
>>>>>> </li>
>>>>>> + <li>Full featured Test IDE that allows faster Test Plan
>>>>>> <b>recording, building and debugging</b>.</li>
>>>>>> + <li><b><a href="usermanual/get-started.html#non_gui">CLI mode
>>>>>> (NON
>>>>>> GUI)</a></b> to load test from any Java compatible OS (Windows, Linux,
>>>>>> Mac)</li>
>>>>>> + <li>Analysis of Load Test thanks to a clear, complete and dynamic
>>>>>> <b><a href="usermanual/generating-dashboard.html" >ready to present
>>>>>> HTML
>>>>>> report</a></b></li>
>>>>>> + <li>Easy correlation for most popular formats, <b><a
>>>>>> href="usermanual/component_reference.html#CSS/JQuery_Extractor"
>>>>>>
>>>>>> HTML</a>, <a href="usermanual/component_ref
>>>>>>> erence.html#JSON_Extractor"
>>>>>>> JSON </a>,
>>>>>>>
>>>>>>> + <a href="usermanual/component_ref
>>>>>> erence.html#XPath_Extractor"
>>>>>>
>>>>>> XML</a> or <a href="usermanual/component_ref
>>>>>>>
>>>>>>> erence.html#Regular_Expression_Extractor" >any textual
>>>>>> format</a></b></li>
>>>>>> <li>Complete portability and <b>100% Java purity</b>.</li>
>>>>>> - <li>Full <b>multithreading</b> framework allows concurrent
>>>>>> sampling
>>>>>> by many threads and
>>>>>> + <li>Full <b>multi-threading</b> framework allows concurrent
>>>>>> sampling
>>>>>> by many threads and
>>>>>> simultaneous sampling of different functions by separate
>>>>>> thread
>>>>>> groups.</li>
>>>>>> - <li>Careful <b>GUI</b> design allows faster Test Plan building
>>>>>> and
>>>>>> debugging.</li>
>>>>>> <li>Caching and offline analysis/replaying of test
>>>>>> results.</li>
>>>>>> <li><b>Highly Extensible core:</b>
>>>>>> <ul>
>>>>>> @@ -69,20 +71,10 @@ behavior under heavy concurrent load.
>>>>>> <li>Data analysis and <b>visualization plugins</b> allow
>>>>>> great
>>>>>> extensibility
>>>>>> as well as personalization.</li>
>>>>>> <li>Functions can be used to provide dynamic input to a
>>>>>> test
>>>>>> or
>>>>>> provide data manipulation.</li>
>>>>>> - <li><b>Scriptable Samplers</b> (BeanShell, BSF-compatible
>>>>>> languages and JSR223-compatible languages)</li>
>>>>>> + <li><b>Scriptable Samplers</b> (JSR223-compatible languages
>>>>>> (<a
>>>>>> href="http://groovy-lang.org">Groovy</a>) and BeanShell)</li>
>>>>>> </ul>
>>>>>> </li>
>>>>>> </ul>
>>>>>> -<h2>JMeter is not a browser</h2>
>>>>>> -<p>
>>>>>> -JMeter is not a browser.
>>>>>> -As far as web-services and remote services are concerned, JMeter
>>>>>> looks
>>>>>> like a browser (or rather, multiple browsers);
>>>>>> -however JMeter does not perform all the actions supported by
>>>>>> browsers.
>>>>>> -In particular, JMeter does not execute the Javascript found in HTML
>>>>>> pages.
>>>>>> -Nor does it render the HTML pages as a browser does
>>>>>> -(it's possible to view the response as HTML etc., but the timings are
>>>>>> not included in any samples, and only one sample in one thread is ever
>>>>>> viewed at a time).
>>>>>> -</p>
>>>>>> -
>>>>>> <h2>How do I do it?</h2>
>>>>>> <ul>
>>>>>> <li><a href="usermanual/index.html">Using JMeter</a> to
>>>>>> understand
>>>>>> how
>>>>>> to use JMeter</li>
>>>>>> @@ -94,6 +86,17 @@ Nor does it render the HTML pages as a b
>>>>>> <li><a href="http://wiki.apache.org/jmeter/">JMeter Wiki</a></li>
>>>>>> <li><a href="building.html">Building JMeter and Add-Ons</a> for
>>>>>> advanced usage</li>
>>>>>> </ul>
>>>>>> +
>>>>>> +<h2>JMeter is not a browser</h2>
>>>>>> +<p>
>>>>>> +JMeter is not a browser, it works at protocol level.
>>>>>> +As far as web-services and remote services are concerned, JMeter
>>>>>> looks
>>>>>> like a browser (or rather, multiple browsers);
>>>>>> +however JMeter does not perform all the actions supported by
>>>>>> browsers.
>>>>>> +In particular, JMeter does not execute the Javascript found in HTML
>>>>>> pages.
>>>>>> +Nor does it render the HTML pages as a browser does
>>>>>> +(it's possible to view the response as HTML etc., but the timings are
>>>>>> not included in any samples, and only one sample in one thread is ever
>>>>>> viewed at a time).
>>>>>> +</p>
>>>>>> +
>>>>>> <h2>Tutorials (PDF)</h2>
>>>>>> <ul>
>>>>>> <li><a href="usermanual/jmeter_distributed_testing_step_by_step.
>>>>>> pdf">Distributed
>>>>>> Testing</a></li>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>
--
Cordialement.
Philippe Mouawad.
Re: svn commit: r1767314 - /jmeter/trunk/xdocs/index.xml
Posted by Milamber <mi...@apache.org>.
On 03/11/2016 12:06, Philippe Mouawad wrote:
> On Thursday, November 3, 2016, Milamber <mi...@apache.org> wrote:
>
>> I agree that Non-GUI isn't the good words to say "launch JMeter without
>> graphical interface"
>>
>> But the "CLI mode" (cli + mode) isn't too the good words to say "launch
>> JMeter without graphical interface and for heavy load tests"
>>
>> Perhaps change the "CLI Mode" to "Headless mode" (seems to be the good
>> word)
>>
>> https://en.wikipedia.org/wiki/Headless_software
> -1 for me . It's not clear.
>
> i prefer cli also for marketing reasons also.
"command-line mode" ? sound good for you ?
>
>
>>
>> On 02/11/2016 21:27, Philippe Mouawad wrote:
>>
>>> For me, Non gui has no meaning for newbies .
>>> I think cli is ok and understandable , since afaik we use an avalon
>>> version
>>> of cli that we should probably migrate one day to commons-cli from apache.
>>>
>>> I still see (on twitter, stackoverflow, private mails) a lot of newbies
>>> and
>>> even users not being aware of the non gui mode and I think it's due to the
>>> name. Clo is more meaningful.
>>>
>>> We must make it clear that cli is for load testing, gui for
>>> building/debugging.
>>>
>>> Regards
>>>
>>> On Wednesday, November 2, 2016, Milamber <mi...@apache.org> wrote:
>>>
>>> + <li><b><a href="usermanual/get-started.html#non_gui">CLI mode (NON
>>>>> GUI)</a></b> to load test from any Java compatible OS (Windows, Linux,
>>>>> Mac)</li>
>>>>>
>>>>>
>>>> I'm not sure that the CLI mode = Non GUI.
>>>> In my mind, the CLI mode is a command line mode to have interactive
>>>> actions with JMeter with command line (like bash in Linux, or wsadmin.sh
>>>> with WebSphere, or jboss-cli.sh with JBoss)
>>>>
>>>> CLI means : command-line interface or command language interpreter (so
>>>> means that JMeter a CLI interperter ?)
>>>>
>>>> https://en.wikipedia.org/wiki/Command-line_interface
>>>>
>>>>
>>>>
>>>>
>>>> On 31/10/2016 15:51, pmouawad@apache.org wrote:
>>>>
>>>> Author: pmouawad
>>>>> Date: Mon Oct 31 15:51:15 2016
>>>>> New Revision: 1767314
>>>>>
>>>>> URL: http://svn.apache.org/viewvc?rev=1767314&view=rev
>>>>> Log:
>>>>> Rework presentation
>>>>> Highlight features
>>>>>
>>>>> Modified:
>>>>> jmeter/trunk/xdocs/index.xml
>>>>>
>>>>> Modified: jmeter/trunk/xdocs/index.xml
>>>>> URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/index.xml?re
>>>>> v=1767314&r1=1767313&r2=1767314&view=diff
>>>>> ============================================================
>>>>> ==================
>>>>> --- jmeter/trunk/xdocs/index.xml (original)
>>>>> +++ jmeter/trunk/xdocs/index.xml Mon Oct 31 15:51:15 2016
>>>>> @@ -34,20 +34,17 @@
>>>>> <h2>What can I do with it?</h2>
>>>>> <p>
>>>>> Apache JMeter may be used to test performance both on static
>>>>> and
>>>>> dynamic
>>>>> - resources (Webservices (SOAP/REST), Web dynamic languages - PHP,
>>>>> Java, ASP.NET, Files, etc. -, Java Objects, Data Bases and
>>>>> - Queries, FTP Servers and more). It can be used to simulate a
>>>>> heavy
>>>>> -load on a server, group of servers, network or object to test its
>>>>> strength or to analyze
>>>>> -overall performance under different load types. You can use it to make
>>>>> a
>>>>> -graphical analysis of performance or to test your server/script/object
>>>>> -behavior under heavy concurrent load.
>>>>> -</p>
>>>>> -<h2>What does it do?</h2>
>>>>> + resources , Web dynamic applications. <br/>
>>>>> + It can be used to simulate a heavy load on a server, group of
>>>>> servers,
>>>>> + network or object to test its strength or to analyze overall
>>>>> performance
>>>>> + under different load types.<br/>
>>>>> + </p>
>>>>> <p>Apache JMeter features include:</p>
>>>>> <ul>
>>>>> - <li>Ability to load and performance test many different
>>>>> server/protocol types:
>>>>> + <li>Ability to load and performance test many different
>>>>> applications/server/protocol types:
>>>>> <ul>
>>>>> - <li>Web - HTTP, HTTPS</li>
>>>>> - <li>SOAP / REST</li>
>>>>> + <li>Web - HTTP, HTTPS (Java, NodeJS, PHP, ASP.NET...)</li>
>>>>> + <li>SOAP / REST Webservices</li>
>>>>> <li>FTP</li>
>>>>> <li>Database via JDBC</li>
>>>>> <li>LDAP</li>
>>>>> @@ -55,12 +52,17 @@ behavior under heavy concurrent load.
>>>>> <li>Mail - SMTP(S), POP3(S) and IMAP(S)</li>
>>>>> <li>Native commands or shell scripts</li>
>>>>> <li>TCP</li>
>>>>> + <li>Java Objects</li>
>>>>> </ul>
>>>>> </li>
>>>>> + <li>Full featured Test IDE that allows faster Test Plan
>>>>> <b>recording, building and debugging</b>.</li>
>>>>> + <li><b><a href="usermanual/get-started.html#non_gui">CLI mode (NON
>>>>> GUI)</a></b> to load test from any Java compatible OS (Windows, Linux,
>>>>> Mac)</li>
>>>>> + <li>Analysis of Load Test thanks to a clear, complete and dynamic
>>>>> <b><a href="usermanual/generating-dashboard.html" >ready to present
>>>>> HTML
>>>>> report</a></b></li>
>>>>> + <li>Easy correlation for most popular formats, <b><a
>>>>> href="usermanual/component_reference.html#CSS/JQuery_Extractor"
>>>>>
>>>>>> HTML</a>, <a href="usermanual/component_reference.html#JSON_Extractor"
>>>>>> JSON </a>,
>>>>>>
>>>>> + <a href="usermanual/component_reference.html#XPath_Extractor"
>>>>>
>>>>>> XML</a> or <a href="usermanual/component_ref
>>>>>>
>>>>> erence.html#Regular_Expression_Extractor" >any textual
>>>>> format</a></b></li>
>>>>> <li>Complete portability and <b>100% Java purity</b>.</li>
>>>>> - <li>Full <b>multithreading</b> framework allows concurrent sampling
>>>>> by many threads and
>>>>> + <li>Full <b>multi-threading</b> framework allows concurrent
>>>>> sampling
>>>>> by many threads and
>>>>> simultaneous sampling of different functions by separate
>>>>> thread
>>>>> groups.</li>
>>>>> - <li>Careful <b>GUI</b> design allows faster Test Plan building and
>>>>> debugging.</li>
>>>>> <li>Caching and offline analysis/replaying of test results.</li>
>>>>> <li><b>Highly Extensible core:</b>
>>>>> <ul>
>>>>> @@ -69,20 +71,10 @@ behavior under heavy concurrent load.
>>>>> <li>Data analysis and <b>visualization plugins</b> allow
>>>>> great
>>>>> extensibility
>>>>> as well as personalization.</li>
>>>>> <li>Functions can be used to provide dynamic input to a test
>>>>> or
>>>>> provide data manipulation.</li>
>>>>> - <li><b>Scriptable Samplers</b> (BeanShell, BSF-compatible
>>>>> languages and JSR223-compatible languages)</li>
>>>>> + <li><b>Scriptable Samplers</b> (JSR223-compatible languages (<a
>>>>> href="http://groovy-lang.org">Groovy</a>) and BeanShell)</li>
>>>>> </ul>
>>>>> </li>
>>>>> </ul>
>>>>> -<h2>JMeter is not a browser</h2>
>>>>> -<p>
>>>>> -JMeter is not a browser.
>>>>> -As far as web-services and remote services are concerned, JMeter looks
>>>>> like a browser (or rather, multiple browsers);
>>>>> -however JMeter does not perform all the actions supported by browsers.
>>>>> -In particular, JMeter does not execute the Javascript found in HTML
>>>>> pages.
>>>>> -Nor does it render the HTML pages as a browser does
>>>>> -(it's possible to view the response as HTML etc., but the timings are
>>>>> not included in any samples, and only one sample in one thread is ever
>>>>> viewed at a time).
>>>>> -</p>
>>>>> -
>>>>> <h2>How do I do it?</h2>
>>>>> <ul>
>>>>> <li><a href="usermanual/index.html">Using JMeter</a> to understand
>>>>> how
>>>>> to use JMeter</li>
>>>>> @@ -94,6 +86,17 @@ Nor does it render the HTML pages as a b
>>>>> <li><a href="http://wiki.apache.org/jmeter/">JMeter Wiki</a></li>
>>>>> <li><a href="building.html">Building JMeter and Add-Ons</a> for
>>>>> advanced usage</li>
>>>>> </ul>
>>>>> +
>>>>> +<h2>JMeter is not a browser</h2>
>>>>> +<p>
>>>>> +JMeter is not a browser, it works at protocol level.
>>>>> +As far as web-services and remote services are concerned, JMeter looks
>>>>> like a browser (or rather, multiple browsers);
>>>>> +however JMeter does not perform all the actions supported by browsers.
>>>>> +In particular, JMeter does not execute the Javascript found in HTML
>>>>> pages.
>>>>> +Nor does it render the HTML pages as a browser does
>>>>> +(it's possible to view the response as HTML etc., but the timings are
>>>>> not included in any samples, and only one sample in one thread is ever
>>>>> viewed at a time).
>>>>> +</p>
>>>>> +
>>>>> <h2>Tutorials (PDF)</h2>
>>>>> <ul>
>>>>> <li><a href="usermanual/jmeter_distributed_testing_step_by_step.
>>>>> pdf">Distributed
>>>>> Testing</a></li>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
Re: svn commit: r1767314 - /jmeter/trunk/xdocs/index.xml
Posted by Philippe Mouawad <ph...@gmail.com>.
On Thursday, November 3, 2016, Milamber <mi...@apache.org> wrote:
>
> I agree that Non-GUI isn't the good words to say "launch JMeter without
> graphical interface"
>
> But the "CLI mode" (cli + mode) isn't too the good words to say "launch
> JMeter without graphical interface and for heavy load tests"
>
> Perhaps change the "CLI Mode" to "Headless mode" (seems to be the good
> word)
>
> https://en.wikipedia.org/wiki/Headless_software
-1 for me . It's not clear.
i prefer cli also for marketing reasons also.
>
>
> On 02/11/2016 21:27, Philippe Mouawad wrote:
>
>> For me, Non gui has no meaning for newbies .
>> I think cli is ok and understandable , since afaik we use an avalon
>> version
>> of cli that we should probably migrate one day to commons-cli from apache.
>>
>> I still see (on twitter, stackoverflow, private mails) a lot of newbies
>> and
>> even users not being aware of the non gui mode and I think it's due to the
>> name. Clo is more meaningful.
>>
>> We must make it clear that cli is for load testing, gui for
>> building/debugging.
>>
>> Regards
>>
>> On Wednesday, November 2, 2016, Milamber <mi...@apache.org> wrote:
>>
>> + <li><b><a href="usermanual/get-started.html#non_gui">CLI mode (NON
>>>
>>>> GUI)</a></b> to load test from any Java compatible OS (Windows, Linux,
>>>> Mac)</li>
>>>>
>>>>
>>> I'm not sure that the CLI mode = Non GUI.
>>> In my mind, the CLI mode is a command line mode to have interactive
>>> actions with JMeter with command line (like bash in Linux, or wsadmin.sh
>>> with WebSphere, or jboss-cli.sh with JBoss)
>>>
>>> CLI means : command-line interface or command language interpreter (so
>>> means that JMeter a CLI interperter ?)
>>>
>>> https://en.wikipedia.org/wiki/Command-line_interface
>>>
>>>
>>>
>>>
>>> On 31/10/2016 15:51, pmouawad@apache.org wrote:
>>>
>>> Author: pmouawad
>>>> Date: Mon Oct 31 15:51:15 2016
>>>> New Revision: 1767314
>>>>
>>>> URL: http://svn.apache.org/viewvc?rev=1767314&view=rev
>>>> Log:
>>>> Rework presentation
>>>> Highlight features
>>>>
>>>> Modified:
>>>> jmeter/trunk/xdocs/index.xml
>>>>
>>>> Modified: jmeter/trunk/xdocs/index.xml
>>>> URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/index.xml?re
>>>> v=1767314&r1=1767313&r2=1767314&view=diff
>>>> ============================================================
>>>> ==================
>>>> --- jmeter/trunk/xdocs/index.xml (original)
>>>> +++ jmeter/trunk/xdocs/index.xml Mon Oct 31 15:51:15 2016
>>>> @@ -34,20 +34,17 @@
>>>> <h2>What can I do with it?</h2>
>>>> <p>
>>>> Apache JMeter may be used to test performance both on static
>>>> and
>>>> dynamic
>>>> - resources (Webservices (SOAP/REST), Web dynamic languages - PHP,
>>>> Java, ASP.NET, Files, etc. -, Java Objects, Data Bases and
>>>> - Queries, FTP Servers and more). It can be used to simulate a
>>>> heavy
>>>> -load on a server, group of servers, network or object to test its
>>>> strength or to analyze
>>>> -overall performance under different load types. You can use it to make
>>>> a
>>>> -graphical analysis of performance or to test your server/script/object
>>>> -behavior under heavy concurrent load.
>>>> -</p>
>>>> -<h2>What does it do?</h2>
>>>> + resources , Web dynamic applications. <br/>
>>>> + It can be used to simulate a heavy load on a server, group of
>>>> servers,
>>>> + network or object to test its strength or to analyze overall
>>>> performance
>>>> + under different load types.<br/>
>>>> + </p>
>>>> <p>Apache JMeter features include:</p>
>>>> <ul>
>>>> - <li>Ability to load and performance test many different
>>>> server/protocol types:
>>>> + <li>Ability to load and performance test many different
>>>> applications/server/protocol types:
>>>> <ul>
>>>> - <li>Web - HTTP, HTTPS</li>
>>>> - <li>SOAP / REST</li>
>>>> + <li>Web - HTTP, HTTPS (Java, NodeJS, PHP, ASP.NET...)</li>
>>>> + <li>SOAP / REST Webservices</li>
>>>> <li>FTP</li>
>>>> <li>Database via JDBC</li>
>>>> <li>LDAP</li>
>>>> @@ -55,12 +52,17 @@ behavior under heavy concurrent load.
>>>> <li>Mail - SMTP(S), POP3(S) and IMAP(S)</li>
>>>> <li>Native commands or shell scripts</li>
>>>> <li>TCP</li>
>>>> + <li>Java Objects</li>
>>>> </ul>
>>>> </li>
>>>> + <li>Full featured Test IDE that allows faster Test Plan
>>>> <b>recording, building and debugging</b>.</li>
>>>> + <li><b><a href="usermanual/get-started.html#non_gui">CLI mode (NON
>>>> GUI)</a></b> to load test from any Java compatible OS (Windows, Linux,
>>>> Mac)</li>
>>>> + <li>Analysis of Load Test thanks to a clear, complete and dynamic
>>>> <b><a href="usermanual/generating-dashboard.html" >ready to present
>>>> HTML
>>>> report</a></b></li>
>>>> + <li>Easy correlation for most popular formats, <b><a
>>>> href="usermanual/component_reference.html#CSS/JQuery_Extractor"
>>>>
>>>>> HTML</a>, <a href="usermanual/component_reference.html#JSON_Extractor"
>>>>> JSON </a>,
>>>>>
>>>> + <a href="usermanual/component_reference.html#XPath_Extractor"
>>>>
>>>>> XML</a> or <a href="usermanual/component_ref
>>>>>
>>>> erence.html#Regular_Expression_Extractor" >any textual
>>>> format</a></b></li>
>>>> <li>Complete portability and <b>100% Java purity</b>.</li>
>>>> - <li>Full <b>multithreading</b> framework allows concurrent sampling
>>>> by many threads and
>>>> + <li>Full <b>multi-threading</b> framework allows concurrent
>>>> sampling
>>>> by many threads and
>>>> simultaneous sampling of different functions by separate
>>>> thread
>>>> groups.</li>
>>>> - <li>Careful <b>GUI</b> design allows faster Test Plan building and
>>>> debugging.</li>
>>>> <li>Caching and offline analysis/replaying of test results.</li>
>>>> <li><b>Highly Extensible core:</b>
>>>> <ul>
>>>> @@ -69,20 +71,10 @@ behavior under heavy concurrent load.
>>>> <li>Data analysis and <b>visualization plugins</b> allow
>>>> great
>>>> extensibility
>>>> as well as personalization.</li>
>>>> <li>Functions can be used to provide dynamic input to a test
>>>> or
>>>> provide data manipulation.</li>
>>>> - <li><b>Scriptable Samplers</b> (BeanShell, BSF-compatible
>>>> languages and JSR223-compatible languages)</li>
>>>> + <li><b>Scriptable Samplers</b> (JSR223-compatible languages (<a
>>>> href="http://groovy-lang.org">Groovy</a>) and BeanShell)</li>
>>>> </ul>
>>>> </li>
>>>> </ul>
>>>> -<h2>JMeter is not a browser</h2>
>>>> -<p>
>>>> -JMeter is not a browser.
>>>> -As far as web-services and remote services are concerned, JMeter looks
>>>> like a browser (or rather, multiple browsers);
>>>> -however JMeter does not perform all the actions supported by browsers.
>>>> -In particular, JMeter does not execute the Javascript found in HTML
>>>> pages.
>>>> -Nor does it render the HTML pages as a browser does
>>>> -(it's possible to view the response as HTML etc., but the timings are
>>>> not included in any samples, and only one sample in one thread is ever
>>>> viewed at a time).
>>>> -</p>
>>>> -
>>>> <h2>How do I do it?</h2>
>>>> <ul>
>>>> <li><a href="usermanual/index.html">Using JMeter</a> to understand
>>>> how
>>>> to use JMeter</li>
>>>> @@ -94,6 +86,17 @@ Nor does it render the HTML pages as a b
>>>> <li><a href="http://wiki.apache.org/jmeter/">JMeter Wiki</a></li>
>>>> <li><a href="building.html">Building JMeter and Add-Ons</a> for
>>>> advanced usage</li>
>>>> </ul>
>>>> +
>>>> +<h2>JMeter is not a browser</h2>
>>>> +<p>
>>>> +JMeter is not a browser, it works at protocol level.
>>>> +As far as web-services and remote services are concerned, JMeter looks
>>>> like a browser (or rather, multiple browsers);
>>>> +however JMeter does not perform all the actions supported by browsers.
>>>> +In particular, JMeter does not execute the Javascript found in HTML
>>>> pages.
>>>> +Nor does it render the HTML pages as a browser does
>>>> +(it's possible to view the response as HTML etc., but the timings are
>>>> not included in any samples, and only one sample in one thread is ever
>>>> viewed at a time).
>>>> +</p>
>>>> +
>>>> <h2>Tutorials (PDF)</h2>
>>>> <ul>
>>>> <li><a href="usermanual/jmeter_distributed_testing_step_by_step.
>>>> pdf">Distributed
>>>> Testing</a></li>
>>>>
>>>>
>>>>
>>>>
>>>>
>
--
Cordialement.
Philippe Mouawad.
Re: svn commit: r1767314 - /jmeter/trunk/xdocs/index.xml
Posted by Milamber <mi...@apache.org>.
I agree that Non-GUI isn't the good words to say "launch JMeter without
graphical interface"
But the "CLI mode" (cli + mode) isn't too the good words to say "launch
JMeter without graphical interface and for heavy load tests"
Perhaps change the "CLI Mode" to "Headless mode" (seems to be the good word)
https://en.wikipedia.org/wiki/Headless_software
On 02/11/2016 21:27, Philippe Mouawad wrote:
> For me, Non gui has no meaning for newbies .
> I think cli is ok and understandable , since afaik we use an avalon version
> of cli that we should probably migrate one day to commons-cli from apache.
>
> I still see (on twitter, stackoverflow, private mails) a lot of newbies and
> even users not being aware of the non gui mode and I think it's due to the
> name. Clo is more meaningful.
>
> We must make it clear that cli is for load testing, gui for
> building/debugging.
>
> Regards
>
> On Wednesday, November 2, 2016, Milamber <mi...@apache.org> wrote:
>
>> + <li><b><a href="usermanual/get-started.html#non_gui">CLI mode (NON
>>> GUI)</a></b> to load test from any Java compatible OS (Windows, Linux,
>>> Mac)</li>
>>>
>>
>> I'm not sure that the CLI mode = Non GUI.
>> In my mind, the CLI mode is a command line mode to have interactive
>> actions with JMeter with command line (like bash in Linux, or wsadmin.sh
>> with WebSphere, or jboss-cli.sh with JBoss)
>>
>> CLI means : command-line interface or command language interpreter (so
>> means that JMeter a CLI interperter ?)
>>
>> https://en.wikipedia.org/wiki/Command-line_interface
>>
>>
>>
>>
>> On 31/10/2016 15:51, pmouawad@apache.org wrote:
>>
>>> Author: pmouawad
>>> Date: Mon Oct 31 15:51:15 2016
>>> New Revision: 1767314
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1767314&view=rev
>>> Log:
>>> Rework presentation
>>> Highlight features
>>>
>>> Modified:
>>> jmeter/trunk/xdocs/index.xml
>>>
>>> Modified: jmeter/trunk/xdocs/index.xml
>>> URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/index.xml?re
>>> v=1767314&r1=1767313&r2=1767314&view=diff
>>> ============================================================
>>> ==================
>>> --- jmeter/trunk/xdocs/index.xml (original)
>>> +++ jmeter/trunk/xdocs/index.xml Mon Oct 31 15:51:15 2016
>>> @@ -34,20 +34,17 @@
>>> <h2>What can I do with it?</h2>
>>> <p>
>>> Apache JMeter may be used to test performance both on static and
>>> dynamic
>>> - resources (Webservices (SOAP/REST), Web dynamic languages - PHP,
>>> Java, ASP.NET, Files, etc. -, Java Objects, Data Bases and
>>> - Queries, FTP Servers and more). It can be used to simulate a heavy
>>> -load on a server, group of servers, network or object to test its
>>> strength or to analyze
>>> -overall performance under different load types. You can use it to make a
>>> -graphical analysis of performance or to test your server/script/object
>>> -behavior under heavy concurrent load.
>>> -</p>
>>> -<h2>What does it do?</h2>
>>> + resources , Web dynamic applications. <br/>
>>> + It can be used to simulate a heavy load on a server, group of
>>> servers,
>>> + network or object to test its strength or to analyze overall
>>> performance
>>> + under different load types.<br/>
>>> + </p>
>>> <p>Apache JMeter features include:</p>
>>> <ul>
>>> - <li>Ability to load and performance test many different
>>> server/protocol types:
>>> + <li>Ability to load and performance test many different
>>> applications/server/protocol types:
>>> <ul>
>>> - <li>Web - HTTP, HTTPS</li>
>>> - <li>SOAP / REST</li>
>>> + <li>Web - HTTP, HTTPS (Java, NodeJS, PHP, ASP.NET...)</li>
>>> + <li>SOAP / REST Webservices</li>
>>> <li>FTP</li>
>>> <li>Database via JDBC</li>
>>> <li>LDAP</li>
>>> @@ -55,12 +52,17 @@ behavior under heavy concurrent load.
>>> <li>Mail - SMTP(S), POP3(S) and IMAP(S)</li>
>>> <li>Native commands or shell scripts</li>
>>> <li>TCP</li>
>>> + <li>Java Objects</li>
>>> </ul>
>>> </li>
>>> + <li>Full featured Test IDE that allows faster Test Plan
>>> <b>recording, building and debugging</b>.</li>
>>> + <li><b><a href="usermanual/get-started.html#non_gui">CLI mode (NON
>>> GUI)</a></b> to load test from any Java compatible OS (Windows, Linux,
>>> Mac)</li>
>>> + <li>Analysis of Load Test thanks to a clear, complete and dynamic
>>> <b><a href="usermanual/generating-dashboard.html" >ready to present HTML
>>> report</a></b></li>
>>> + <li>Easy correlation for most popular formats, <b><a
>>> href="usermanual/component_reference.html#CSS/JQuery_Extractor"
>>>> HTML</a>, <a href="usermanual/component_reference.html#JSON_Extractor"
>>>> JSON </a>,
>>> + <a href="usermanual/component_reference.html#XPath_Extractor"
>>>> XML</a> or <a href="usermanual/component_ref
>>> erence.html#Regular_Expression_Extractor" >any textual
>>> format</a></b></li>
>>> <li>Complete portability and <b>100% Java purity</b>.</li>
>>> - <li>Full <b>multithreading</b> framework allows concurrent sampling
>>> by many threads and
>>> + <li>Full <b>multi-threading</b> framework allows concurrent sampling
>>> by many threads and
>>> simultaneous sampling of different functions by separate thread
>>> groups.</li>
>>> - <li>Careful <b>GUI</b> design allows faster Test Plan building and
>>> debugging.</li>
>>> <li>Caching and offline analysis/replaying of test results.</li>
>>> <li><b>Highly Extensible core:</b>
>>> <ul>
>>> @@ -69,20 +71,10 @@ behavior under heavy concurrent load.
>>> <li>Data analysis and <b>visualization plugins</b> allow great
>>> extensibility
>>> as well as personalization.</li>
>>> <li>Functions can be used to provide dynamic input to a test or
>>> provide data manipulation.</li>
>>> - <li><b>Scriptable Samplers</b> (BeanShell, BSF-compatible
>>> languages and JSR223-compatible languages)</li>
>>> + <li><b>Scriptable Samplers</b> (JSR223-compatible languages (<a
>>> href="http://groovy-lang.org">Groovy</a>) and BeanShell)</li>
>>> </ul>
>>> </li>
>>> </ul>
>>> -<h2>JMeter is not a browser</h2>
>>> -<p>
>>> -JMeter is not a browser.
>>> -As far as web-services and remote services are concerned, JMeter looks
>>> like a browser (or rather, multiple browsers);
>>> -however JMeter does not perform all the actions supported by browsers.
>>> -In particular, JMeter does not execute the Javascript found in HTML
>>> pages.
>>> -Nor does it render the HTML pages as a browser does
>>> -(it's possible to view the response as HTML etc., but the timings are
>>> not included in any samples, and only one sample in one thread is ever
>>> viewed at a time).
>>> -</p>
>>> -
>>> <h2>How do I do it?</h2>
>>> <ul>
>>> <li><a href="usermanual/index.html">Using JMeter</a> to understand how
>>> to use JMeter</li>
>>> @@ -94,6 +86,17 @@ Nor does it render the HTML pages as a b
>>> <li><a href="http://wiki.apache.org/jmeter/">JMeter Wiki</a></li>
>>> <li><a href="building.html">Building JMeter and Add-Ons</a> for
>>> advanced usage</li>
>>> </ul>
>>> +
>>> +<h2>JMeter is not a browser</h2>
>>> +<p>
>>> +JMeter is not a browser, it works at protocol level.
>>> +As far as web-services and remote services are concerned, JMeter looks
>>> like a browser (or rather, multiple browsers);
>>> +however JMeter does not perform all the actions supported by browsers.
>>> +In particular, JMeter does not execute the Javascript found in HTML
>>> pages.
>>> +Nor does it render the HTML pages as a browser does
>>> +(it's possible to view the response as HTML etc., but the timings are
>>> not included in any samples, and only one sample in one thread is ever
>>> viewed at a time).
>>> +</p>
>>> +
>>> <h2>Tutorials (PDF)</h2>
>>> <ul>
>>> <li><a href="usermanual/jmeter_distributed_testing_step_by_step.pdf">Distributed
>>> Testing</a></li>
>>>
>>>
>>>
>>>
Re: svn commit: r1767314 - /jmeter/trunk/xdocs/index.xml
Posted by Philippe Mouawad <ph...@gmail.com>.
For me, Non gui has no meaning for newbies .
I think cli is ok and understandable , since afaik we use an avalon version
of cli that we should probably migrate one day to commons-cli from apache.
I still see (on twitter, stackoverflow, private mails) a lot of newbies and
even users not being aware of the non gui mode and I think it's due to the
name. Clo is more meaningful.
We must make it clear that cli is for load testing, gui for
building/debugging.
Regards
On Wednesday, November 2, 2016, Milamber <mi...@apache.org> wrote:
>
> + <li><b><a href="usermanual/get-started.html#non_gui">CLI mode (NON
>> GUI)</a></b> to load test from any Java compatible OS (Windows, Linux,
>> Mac)</li>
>>
>
>
> I'm not sure that the CLI mode = Non GUI.
> In my mind, the CLI mode is a command line mode to have interactive
> actions with JMeter with command line (like bash in Linux, or wsadmin.sh
> with WebSphere, or jboss-cli.sh with JBoss)
>
> CLI means : command-line interface or command language interpreter (so
> means that JMeter a CLI interperter ?)
>
> https://en.wikipedia.org/wiki/Command-line_interface
>
>
>
>
> On 31/10/2016 15:51, pmouawad@apache.org wrote:
>
>> Author: pmouawad
>> Date: Mon Oct 31 15:51:15 2016
>> New Revision: 1767314
>>
>> URL: http://svn.apache.org/viewvc?rev=1767314&view=rev
>> Log:
>> Rework presentation
>> Highlight features
>>
>> Modified:
>> jmeter/trunk/xdocs/index.xml
>>
>> Modified: jmeter/trunk/xdocs/index.xml
>> URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/index.xml?re
>> v=1767314&r1=1767313&r2=1767314&view=diff
>> ============================================================
>> ==================
>> --- jmeter/trunk/xdocs/index.xml (original)
>> +++ jmeter/trunk/xdocs/index.xml Mon Oct 31 15:51:15 2016
>> @@ -34,20 +34,17 @@
>> <h2>What can I do with it?</h2>
>> <p>
>> Apache JMeter may be used to test performance both on static and
>> dynamic
>> - resources (Webservices (SOAP/REST), Web dynamic languages - PHP,
>> Java, ASP.NET, Files, etc. -, Java Objects, Data Bases and
>> - Queries, FTP Servers and more). It can be used to simulate a heavy
>> -load on a server, group of servers, network or object to test its
>> strength or to analyze
>> -overall performance under different load types. You can use it to make a
>> -graphical analysis of performance or to test your server/script/object
>> -behavior under heavy concurrent load.
>> -</p>
>> -<h2>What does it do?</h2>
>> + resources , Web dynamic applications. <br/>
>> + It can be used to simulate a heavy load on a server, group of
>> servers,
>> + network or object to test its strength or to analyze overall
>> performance
>> + under different load types.<br/>
>> + </p>
>> <p>Apache JMeter features include:</p>
>> <ul>
>> - <li>Ability to load and performance test many different
>> server/protocol types:
>> + <li>Ability to load and performance test many different
>> applications/server/protocol types:
>> <ul>
>> - <li>Web - HTTP, HTTPS</li>
>> - <li>SOAP / REST</li>
>> + <li>Web - HTTP, HTTPS (Java, NodeJS, PHP, ASP.NET...)</li>
>> + <li>SOAP / REST Webservices</li>
>> <li>FTP</li>
>> <li>Database via JDBC</li>
>> <li>LDAP</li>
>> @@ -55,12 +52,17 @@ behavior under heavy concurrent load.
>> <li>Mail - SMTP(S), POP3(S) and IMAP(S)</li>
>> <li>Native commands or shell scripts</li>
>> <li>TCP</li>
>> + <li>Java Objects</li>
>> </ul>
>> </li>
>> + <li>Full featured Test IDE that allows faster Test Plan
>> <b>recording, building and debugging</b>.</li>
>> + <li><b><a href="usermanual/get-started.html#non_gui">CLI mode (NON
>> GUI)</a></b> to load test from any Java compatible OS (Windows, Linux,
>> Mac)</li>
>> + <li>Analysis of Load Test thanks to a clear, complete and dynamic
>> <b><a href="usermanual/generating-dashboard.html" >ready to present HTML
>> report</a></b></li>
>> + <li>Easy correlation for most popular formats, <b><a
>> href="usermanual/component_reference.html#CSS/JQuery_Extractor"
>> >HTML</a>, <a href="usermanual/component_reference.html#JSON_Extractor"
>> >JSON </a>,
>> + <a href="usermanual/component_reference.html#XPath_Extractor"
>> >XML</a> or <a href="usermanual/component_ref
>> erence.html#Regular_Expression_Extractor" >any textual
>> format</a></b></li>
>> <li>Complete portability and <b>100% Java purity</b>.</li>
>> - <li>Full <b>multithreading</b> framework allows concurrent sampling
>> by many threads and
>> + <li>Full <b>multi-threading</b> framework allows concurrent sampling
>> by many threads and
>> simultaneous sampling of different functions by separate thread
>> groups.</li>
>> - <li>Careful <b>GUI</b> design allows faster Test Plan building and
>> debugging.</li>
>> <li>Caching and offline analysis/replaying of test results.</li>
>> <li><b>Highly Extensible core:</b>
>> <ul>
>> @@ -69,20 +71,10 @@ behavior under heavy concurrent load.
>> <li>Data analysis and <b>visualization plugins</b> allow great
>> extensibility
>> as well as personalization.</li>
>> <li>Functions can be used to provide dynamic input to a test or
>> provide data manipulation.</li>
>> - <li><b>Scriptable Samplers</b> (BeanShell, BSF-compatible
>> languages and JSR223-compatible languages)</li>
>> + <li><b>Scriptable Samplers</b> (JSR223-compatible languages (<a
>> href="http://groovy-lang.org">Groovy</a>) and BeanShell)</li>
>> </ul>
>> </li>
>> </ul>
>> -<h2>JMeter is not a browser</h2>
>> -<p>
>> -JMeter is not a browser.
>> -As far as web-services and remote services are concerned, JMeter looks
>> like a browser (or rather, multiple browsers);
>> -however JMeter does not perform all the actions supported by browsers.
>> -In particular, JMeter does not execute the Javascript found in HTML
>> pages.
>> -Nor does it render the HTML pages as a browser does
>> -(it's possible to view the response as HTML etc., but the timings are
>> not included in any samples, and only one sample in one thread is ever
>> viewed at a time).
>> -</p>
>> -
>> <h2>How do I do it?</h2>
>> <ul>
>> <li><a href="usermanual/index.html">Using JMeter</a> to understand how
>> to use JMeter</li>
>> @@ -94,6 +86,17 @@ Nor does it render the HTML pages as a b
>> <li><a href="http://wiki.apache.org/jmeter/">JMeter Wiki</a></li>
>> <li><a href="building.html">Building JMeter and Add-Ons</a> for
>> advanced usage</li>
>> </ul>
>> +
>> +<h2>JMeter is not a browser</h2>
>> +<p>
>> +JMeter is not a browser, it works at protocol level.
>> +As far as web-services and remote services are concerned, JMeter looks
>> like a browser (or rather, multiple browsers);
>> +however JMeter does not perform all the actions supported by browsers.
>> +In particular, JMeter does not execute the Javascript found in HTML
>> pages.
>> +Nor does it render the HTML pages as a browser does
>> +(it's possible to view the response as HTML etc., but the timings are
>> not included in any samples, and only one sample in one thread is ever
>> viewed at a time).
>> +</p>
>> +
>> <h2>Tutorials (PDF)</h2>
>> <ul>
>> <li><a href="usermanual/jmeter_distributed_testing_step_by_step.pdf">Distributed
>> Testing</a></li>
>>
>>
>>
>>
>
--
Cordialement.
Philippe Mouawad.