Grinder documentation saying lot of benefits of TCPProxy console. Like, record the response, auto generate the Jython test scripts and a lot. I am very happy for that. Sorry to say, but I am not able to find how to use it. Like, I see some thing 'Insert command and press enter' text box and 'insert command' button. But I did not find any details, what should I write in that text box. And how to use TCPProxy Console.
But Grinder Documentation showing some generated scripts also. But how it generated, I did not find any details.
Please help me, if any body know.
TCPProxy Console is very easy to use than I expected. It is some thing like Selenium Mozilla Firefox plugin.
One of friends from grinder-user gave a solution. I hope it will helpful to you also.
Start TCP Proxy (details in the above doc), default port is 8001.
Configure browser to use the localhost:8001 port so HTTP traffic generated by your browser goes through TCP Proxy
Run the steps in the browser for the testcase
Click STOP on the TCP Proxy dialog and the resulting grinder script will be generated
Related
I am having problem with chimp.js configuration. When I run tests the browser is not using provided host / post. I tried many things but without success. Does anyone know how to set up it properly? Please find my config in screenshot provided.
When the browser first starts, it defaults to data;. You need to navigate somewhere first.
The host and port settings are not related to browsing. They tell Chimp where the Selenium server is, which by default is chromedriver.
I had to setup beforeFeature hook to start using localhost:3000
I am new to RFT and i just want simple script to open browser and close the same using RFT.
I tried to find solution on internet but there were solutions which i can't digest.
Help me out on this
First, you need to enable your browser. Then configure your application. After that you can use the recorder to start your configured application (this starts the browser if it is a web application) and you can also use the recorder to record the close browser action.
For starting your browser the generated code will be something like this:
startApp("nameOfTheAppYouConfigured");
For closing:
browser_htmlBrowser(document_YourDocument(), MAY_EXIT).close();
BTW: What is so difficult in following a guide like this or just using the RFT tutorials...
I am having jmeter to perform testing. However I have visited to some while doing the testing. when I have view the result of the same in that except the grid table data it shows the every details on the web page. I am having jmeter 3.0 installed on windows 10 64 bit.
Thanks for replay
as you said i have change the path from "/ntes/specialTrains.jsp"
and made http request default as "enquiry.indianrail.gov.in"
Error message is not displayed, but still not able to get the grid in the output.
attached the screen shot please have look.
"Issue is still not resolved. so please assist for the same"
I'm not fully getting your answer, however here is a couple of advices:
You won't be able to see the JMeter Variable originating from the XPath Extractor in the View Results Tree listener unless you add a Debug Sampler to your Test Plan. View Results Tree listener itself has XPath Tester mode where you can evaluate your XPath queries directly against the "live" response without having to re-run the request. See How to Debug your Apache JMeter Script article for above instructions explained in details.
Your 2nd request is misconfigured. It should look as follows:
Server Name or IP: enquiry.ingianrail.gov.in
Path: /ntes/specialTrains.jsp
Actually the easiest way to get JMeter test script "skeleton" and avoiding errors like above is just recording it via JMeter's built-in proxy server. See JMeter Proxy Step by Step guide for instructions.
Pretty much exactly what it says on the tin: I have a Loadrunner script and I would like to convert it to a Neoload one. There's no way to do this automatically, obviously, but my idea was to capture traffic created by a loadrunner playthrough and then somehow reroute it (or export it?) to Neoload, and then do the manual extraction/whatever later.
The answer given here gives some tantalizing hints on how to do it, but the problem is that I can't figure out how to get Neoload to accept anything other than manual recording (the answer is given for Webtest because Fiddler can export a Webtest file, but there's no such option for Neoload). Is there a viable way to make this approach work, or is there a different option I could explore?
NeoLoad records the HTTP traffic through a Proxy (default recording method). All you need to do is:
Tell LoadRunner to play the script through a Proxy: NeoLoad machine, port 8090 (default NeoLoad recording port)
Launch a NeoLoad recording (you can uncheck "Launch Browser")
Launch the LoadRunner playback of 1 VU
Stop NeoLoad recording
I hope this helps,
Christophe
Neotys
There no good conversion between the scripts.
Creating a script in that way would generate only the HTTP requests.
It would NOT generate:
1. Script changes (conditions, loops, etc)
2. Library attachments
3. Parameterizations
4. Validations
and extra stuff
Since Neoload 6.5.0 there is a new tool called
LoadRunner Converter.
The LoadRunner converter provides the capability to convert LoadRunner HTTP scripts to their NeoLoad equivalent for those organizations that currently use LoadRunner and want to move on to NeoLoad.
See:
https://www.neotys.com/neoload/whats-new
I'm trying to find a non-SSL resource that is being loaded on my site.
This happens occasional where one of us forgets to use the https version of a resource (like some js in a CDN).
My question is there any firebug-like tools to find these "Turds in the punch bowl"? I want my green padlock back :)
Besides Firebug, which you've mentioned, you can use the developer tools in Chrome:
Tools menu -> Developer Tools
Go through the list of loaded resources in the Network tab
Alternatively, the HttpFox extension for Firefox can also be useful. It will keep logging the traffic even when you change pages, which may be useful in some cases.
(This is very similar to Firebug.)
mitm-proxy is great for stuff like this - http://crypto.stanford.edu/ssl-mitm/
You run it on your local machine in a console window, set your browser to use it as a proxy, and you can watch /log everything that your browser requests. It's a little noisy since it shows SSL hand-shaking and file contents, but you can filter that down. When you need to debug SSL communications it's invaluable to see those details though..
mitm-proxy is based on http://grinder.sourceforge.net/g3/tcpproxy.html which has more in the way of scripting capabilities.