How can we convert Loadrunner scripts into JMeter scripts [closed] - jmeter

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
Can some one please guide me "How to convert Loadrunner Scripts into JMeter scripts"?
Thanks,
Raj

This tool was released lately.
If you upload a ZIP of your LoadRunner script, it will convert it to JMeter or Selenium.
It might not be 100%, but it will tell you what it couldn't convert and save you a lot of troubles.
shiftleft.blazemeter.com

Record them (will work only for HTTP protocol and derivatives, i.e. Web Services).
JMeter Configuration. The fastest and the easiest way of setting up JMeter for recording is using JMeter Templates Feature.
Select File -> Templates -> Recording -> Create from JMeter's main menu
Expand WorkBench -> HTTP(S) Test Script Recorder and click "Start" button
LoadRunner Configuration
In VuGen press F4 (having your script opened) to get into "RunTime Settings" dialog or use Replay -> Runtime Settings from the main menu
Click Proxy -> Use custom proxy -> Use proxy server and enter localhost as proxy and 8888 as a port (given you run JMeter on the same machine)
Run your script with 1 VU and 1 Iteration. JMeter will capture the requests and convert them into HTTP Request samplers.
That's it.

Related

Working with Golang and a Windows Server Machine [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I am fairly new and interested in the Go programming language. I have the intention of using it to code a simple website that includes a shopping cart.
How to install golang on windows server? Is it the same process as a regular computer?
What steps do I take to deploy the website using the Windows server once it is finished.
To what extend is it required to use html, css, or javascript?
How can I keep the site running on the server for other users in our network/LAN to access it?
Any helpful information regarding web apps and/or windows server machines is appreciated!
This is as much a general dev ops question as it is specific to Go. A lot of things to consider here and everyone will have varying preferences but here are some guidelines I'd recommend:
It's not necessary to install the Go tool chain on your production server. You then have to maintain your Go installation on both your development and production environments and if your production server is a different OS than your Windows computer (eg. a Linux distribution) this will get out of hand quickly. Instead, just develop on your local and cross compile to the OS of your production server.
One thing you will need to keep on your production server is whatever DB you choose to work with your Go program.
You can then sftp or transfer through a method of your choice your compiled binary over to your production server along with your static web files. Once the binary is on your production server you can fire it up when you're SSH'ed in eg. ./programname
Depending on how you want to use Go, you don't need Apache. Use the net/http package to serve up your Html, CSS and JS files. You can transfer these static files over after you've worked on them on your local or you can just keep them in a Github repo and git pull them from your prod server as needed, assuming you've installed git there.
You generally don't need to worry about keeping it "running" on your production server. http.ListenAndServe listens on your port for incoming requests. If your server reboots or shuts downs you can automatically have your compiled binary start up along with it.
You can also work with things like Vagrant, Virtual Box and Ansible for high quality mimicking of your production environment and spinning up new servers according to your desired specs.

What could cause successful FTP transfers to be truncated on a brand new RackSpace SSD server? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I am trying to upgrade my web server. I have created a brand new instance of a latest generation virtual server on RackSpace that uses an SSD. On this brand new instance, I installed the following:
Google Chrome
FileZilla FTP Client
I then connected to a FileZilla FTP Server on a different server, which is hosting 2 image files that I am using to test. I then downloaded the 2 image files, which FileZilla reports as "successfully transferred". However, both of the image files are truncated! What could possibly be causing this?
A few things to note:
This only happens on the new instance if it is using an SSD. If I create an identical instance without the SSD (using SATA instead), the error does not occur.
On the server which is transferring the files, the files are also reported as having been transferred successfully. This server has been used as an FTP server for quite some time without any issues.
If I set up the new SSD instance as an FTP server and upload a bunch of files to it, some of them randomly get truncated by 2-10KB. Out of a ~150MB upload, I may end up with 150-200KB missing. If I transfer them again, a different subset of files gets truncated.
If I throttle the transfer speed on the FTP server to 100KB/s, the 2 image files transfer successfully without getting truncated. If I throttle the transfer speed to 500KB/s, the image files get truncated the same way as if there was no throttling.
Any ideas on how this could be happening?
Update: It is not related to FileZilla. Here is the same issue using ftp on the command line:
The solution is documented here: http://www.rackspace.com/knowledge_center/article/disabling-tcp-offloading-in-windows-server-2012
That article is for Windows Server 2012. In my case, I was using Windows Server 2008. To get to the network adapter properties, go to
Right click on Computer --> Properties
Device Manager
Open up network adapters drop down and right click --> Properties
Go to Advanced tab
Disable everything except UDP Checksum Offload.
Important note: If only some of the options are disabled, you will notice a massive performance degradation. Performance will go back up to normal levels after you have disabled all of the necessary options.
The reason it says that the transfer is complete is because closing the socket is- unfortunately- how FTP defines a completed transfer. (It opens up a data connection and sends the data. Closing the connection means the file is completely sent.)
For some reason, it seems like the connection is prematurely closing.
Personally, to me this does sound really bizarre and it might be a driver problem or hardware problem, but I would try:
1. Try Passive mode FTP. The command line client uses PORT mode by default. PASV is more firewall friendly.
2. Try disabling all software firewalls (like Windows Firewall) and retrying.

Slow Apache Server on EasyPHP [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I am using the EasyPHP DevServer 13.1 VC9 (which has Apache 2.4.4 VC9, MySQL 5.6.11, PHP 5.4.14, PHPmyadmin 3.5.8.1 and xdebug 2.2.2). The Apache server is very moody! Sometimes it works fine, but at other times the pages take ages to load. How do I get around this?
I am developing on my local machine. I am a newbie and any help would be greatly appreciated.
Thanks in advance.
its easy,
added these lines into httpd.conf (you can added these lines anywhere in httpd.conf)
AcceptFilter http none
AcceptFilter https none
What worked for me was to use the IPv4 version of 'localhost' in my hosts file. The 'hosts' file is usually located in the C:\Windows\System32\drivers\etc directory on most systems. Editing the 'hosts' file was a pain in the neck. You can't simply right click or double-click to open the file. You first have to fire up Notepad or your favorite editor using "Run As Administrator" (right-click) and then hunt for the file using the "File -> Open" dialog. Windows prevents editing that file normally (a good thing) but then get in the way of actually editing it (a bad thing).
Anyway, under Windows 7, the following two lines are commented out:
# 127.0.0.1 localhost
# ::1 localhost
Uncomment the first line but leave the second commented:
127.0.0.1 localhost
# ::1 localhost
Save the file. Try loading pages in Apache again. Should be back to normal speed.
Source :
http://cubicspot.blogspot.fr/2010/07/fixing-slow-apache-on-localhost-under.html

Is there a non-installable version of Fiddler, or equivalent? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 2 years ago.
Improve this question
One of my clients is currently waiting for his IT department to install Fiddler on his desktop so that he can debug his web application... Apparently his desktop requires IT Admin rights to install anything.
Is there a non-installable version of Fiddler, i.e. a standalone exe (additional files ok) or an equivalent program that can be run off a thumbdrive or a local folder?
In fact, Fiddler Classic does not need to be installed:
Download Fiddler Classic setup (ie. FiddlerSetup.exe)
Open it with your Archive Manager (ie. 7-Zip)
Open $PLUGINSDIR folder
Open the contained FiddlerSetup.exe (yes again) in your Archive Manager
Extract the files in a folder
Run Fiddler.exe
For Fiddler Everywhere, it is almost the same
Download Fiddler Everywhere (ie. Fiddler Everywhere 1.0.1.exe)
Open it with your Archive Manager (ie. 7-Zip)
Open $PLUGINSDIR folder
Open the contained app-64.7z file in your Archive Manager
Extract the files in a folder
Run Fiddler Everywhere.exe
No, Fiddler doesn't "Add hooks" that require administrative permissions. You can simply copy the Fiddler folder from the Program Files folder onto the desktop of whatever user you want and launch it directly from there.
The only thing that you don't get in an "XCOPY" install is the Fiddler-related buttons in your browsers (e.g. IE and Firefox) because those are set by the installer, and if you don't run the installer, you won't get the browser extensions.
You may try either Burp ( http://portswigger.net/burp/ ) or Web Scarab ( http://www.owasp.org/index.php/Category:OWASP_WebScarab_Project ). Both are written in Java, downloadable as zip Files and don't require admin rights ... but java. If they don't fit you can either try one of the numerous other stand alone web proxys ( http://www.owasp.org/index.php/Phoenix/Tools#HTTP_proxying_.2F_editing ) or a Firefox plugin ( http://www.owasp.org/index.php/Phoenix/Tools#Browser-based_HTTP_tampering_.2F_editing_.2F_replaying ).
If the application is developed with Eclipse: This also has some simple Traffic Monitoring tools
There's a TCP/IP sniffer called SmartSniff that is designed to not require installation.
You may want to try FiddlerCap, which is a light-weight version of Fiddler (using FiddlerCore) in the sense that it captures traffic and saves it to a Fiddler archive. It does require an install by default, but you can avoid that if you:
Install the FiddlerCap download on a different machine first. This basically does an extract only. You can simply distribute the files to the intended target machine.
Add the FiddlerCap folder on the target machine to the PATH environment variable, because it needs to find FiddlerCore.dll in that folder.
Just try to extract contents from Fiddler's installation file as Laymain mentioned. Worked for version 1.0.0.
For example, using WinRAR:
How it looks like:

Looking for a GUI debugger that runs on windows and can remote debug on Linux [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
The current setup is that I'm developing a program for Linux (and debugging the binary with GDB via SSH), but using Eclipse and a remote file mount to do the editing from a Windows box. I'd really love to be able to debug in eclipse but I haven't yet found anything that would work.
Anyone know of anything I should look at?
BTW: I'm willing to use non eclipse tool but can't afford to buy anything.
From http://community.livejournal.com/shlomif_tech/9932.html:
Install CDT - The Eclipse C/C++ Development Tooling.
Set up a C/C++ project so it will build and compile.
Install gdb and gdbserver. The latter does not seem to be available in any Mandriva package and had to be compiled from the gdb source, where it is built by default.
Run gdbserver on the generated executable using a command like gdbserver localhost:10900 ./my-exe
In Eclipse go to Run → "Open Run Dialog...", and go to the upper debugger tab and select gdbserver Debugger in the Debugger drop-down. Afterwards, go to the "Connection" tab under Debugger Options and configure your connection. For my demonstration I've chosen "Type: TCP" "Host: localhost" and "Port number: 10900".
Select the Run → Debug in Eclipse option and start debugging the application.
Using Eclipse (assuming Java) this works great. Just start the program on the linux box with the following options:
-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=3000
Then, in Eclipse, click the down arrow by the bug(debugger) and select debug configurations. Create a new Remote Java Application, and add in the name of the linux box and the port you are using (3000 from above). Once the app is launched, it will wait for you to connect. Simply Click Debug or select the Debug Configuration from the drop down debug menu. Change suspend to 'n' if you don't want it to wait.

Resources