Re: [Grinder-use] Unique test numbers required for each script

[phunkyfish <ro...@ph...>]

I think you'll find that to need to pass the property to "java" and not as an
argument of the class.

The following should work...

java -cp %CLASSPATH% -DHTTPPlugin.initialTest=5000 net.grinder.TCPProxy
-console -http > grinder.py

Remember anything with a "-D" before it is a property and not an argument.

Cheers,

Ross


Sachin Joshi-2 wrote:
> 
> Hello,
> 
>  
> 
> While recording the script files for two different modules, I wanted two
> distinguished unique test nos for each module. I came across following
> section in FAQs on HYPERLINK
> "http://grinder.sourceforge.net/faq.html"http://grinder.sourceforge.net/faq.
> html.
> 
>  
> 
> ----------------------------------------------------------------------------
> ---------------------------
> 
> 
> 3.4.7. How to I set different test numbers for httpscript.py and
> httpscript_tests.py without manually editing the scripts? 
> 
> 
> To do this you need to pass the following parameter to the TCPProxy at
> invokation when recording your scripts:
> 
>   -DHTTPPlugin.initialTest=(integer)
>  
> 
> The setting of the initial test number allows you to set different test
> ranges for scripts with different functions. This is useful if you are
> running these different scripts concurrently and collating the results in
> the same console window.
> 
> For example you could set sales.py to have an initial test number of 2000
> and purchases.py to have an initial test number of 3000 (this assumes that
> sales.py has less than 1000 tests). When you run these scripts
> concurrently
> all results in the console window with a test number of 2xxx relate to
> sales.py and those beginning with 3xxx relate to purchases.py.
> 
> ----------------------------------------------------------------------------
> ---------------------------
> 
>  
> 
> I tried the above by adding above filter to TCPProxy as follows.
> 
>  
> 
> java -cp %CLASSPATH% net.grinder.TCPProxy -console -http
> -DHTTPPlugin.initialTest=5000 > grinder.py
> 
>  
> 
> However, I got following error.
> 
>  
> 
> ----------------------------------------------------------------------------
> ---------------------------
> 
> C:\Grinder\grinder-3.0-beta33\bin>java -cp
> C:\Grinder\grinder-3.0-beta33\lib\grinder.jar; net.grinder.TCPProxy
> -console
> -http -DHTTPPlugin.initialTest
> 
> =5000  1>grinder.py
> 
> Picked up _JAVA_OPTIONS: -Xmx1024m
> 
> 1/30/08 12:56:09 PM (tcpproxy): Error: unrecognised or invalid option.
> 
>  
> 
> Usage:
> 
>   java class net.grinder.TCPProxy <options>
> 
>  
> 
> Commonly used options:
> 
>   [-http [<stylesheet>]]       See below.
> 
>   [-console]                   Display the console.
> 
>   [-requestfilter <filter>]    Add a request filter.
> 
>   [-responsefilter <filter>]   Add a response filter.
> 
>   [-localhost <host name/ip>]  Default is localhost.
> 
>   [-localport <port>]          Default is 8001.
> 
>   [-keystore <file>]           Key store details for
> 
>   [-keystorepassword <pass>]   SSL certificates.
> 
>   [-keystoretype <type>]       Default is JSSE dependent.
> 
>  
> 
> Other options:
> 
>   [-properties <file>]         Properties to pass to the filters.
> 
>   [-remotehost <host name>]    Default is localhost.
> 
>   [-remoteport <port>]         Default is 7001.
> 
>   [-timeout <seconds>]         Proxy engine timeout.
> 
>   [-httpproxy <host> <port>]   Route via HTTP/HTTPS proxy.
> 
>   [-httpsproxy <host> <port>]  Override -httpproxy settings for
> 
>                                HTTPS.
> 
>   [-ssl]                       Use SSL when port forwarding.
> 
>   [-colour]                    Be pretty on ANSI terminals.
> 
>   [-component <class>]         Register a component class with
> 
>                                the filter PicoContainer.
> 
>   [-debug]                     Make filter PicoContainer chatty.
> 
>  
> 
> <filter> is the name of a class that implements
> 
> net.grinder.tools.tcpproxy.TCPProxyFilter or one of NONE, ECHO. The
> default
> is
> 
> ECHO. Multiple filters can be specified for each stream.
> 
>  
> 
> By default, the TCPProxy listens as an HTTP/HTTPS Proxy on
> 
> <localhost:localport>.
> 
>  
> 
> If either -remotehost or -remoteport is specified, the TCPProxy acts a
> simple
> 
> port forwarder between <localhost:localport> and <remotehost:remoteport>.
> 
> Specify -ssl for SSL support.
> 
>  
> 
> -http sets up request and response filters to produce a test script
> suitable
> for
> 
> use with the HTTP plugin. The output can be customised by specifying the
> file
> 
> name of an alternative XSLT style sheet.
> 
>  
> 
> -timeout is how long the TCPProxy will wait for a request before timing
> out
> and
> 
> freeing the local port. The TCPProxy will not time out if there are active
> 
> connections.
> 
>  
> 
> -console displays a simple control window that allows the TCPProxy to be
> 
> shutdown cleanly. This is needed because some shells, e.g. Cygwin bash, do
> not
> 
> allow Java processes to be interrupted cleanly, so filters cannot rely on
> 
> standard shutdown hooks.
> 
>  
> 
> -httpproxy and -httpsproxy allow output to be directed through another
> 
> HTTP/HTTPS proxy; this may help you reach the Internet. These options are
> not
> 
> supported in port forwarding mode.
> 
>  
> 
> Typical usage:
> 
>   java class net.grinder.TCPProxy -http -console > grinder.py
> 
> ----------------------------------------------------------------------------
> ---------------------------
> 
>  
> 
> Did I make any mistake in using the option? Is there any working solution
> available?
> 
>  
> 
> Regards,
> 
> Sachin
> 
> 
> No virus found in this outgoing message.
> Checked by AVG Free Edition. 
> Version: 7.5.516 / Virus Database: 269.19.16/1250 - Release Date:
> 1/29/2008
> 10:20 PM
>  
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> grinder-use mailing list
> gri...@li...
> https://lists.sourceforge.net/lists/listinfo/grinder-use
> 
> 

-- 
View this message in context: http://www.nabble.com/Unique-test-numbers-required-for-each-script-tp15176920p15190663.html
Sent from the Grinder - User mailing list archive at Nabble.com.