Skip to main content

SSH and screen command and JMeter

We all know how useful JMeter distributed testing is when it comes to generating how amount of load from multiple machines. This requires certain ports on remote test agent to be opened so that a centralized JMeter server could talk to them and execute test.
Given the inability to get port opened on aws test agents, I could not employ JMeter distributed testing. Hence I resorted to looping through SSH connection and screen command to execute load test on remote machine. Not an ideal solution but far better than logging in to each test agent and starting test manually.

If you never used screen command then Matt has a quick tutorial on it.
I have load test machine image, it is child’s play to bring up load test agent with exactly same configuration on AWS.

This is how for loop looks like -

for server in ip1 ip2 ip3; do
   ssh -tA <you ssh command here> @$server 'bash -s' < screen.sh
done

screen.sh is shell script which is executed on each ip address mentioned above. you don’t need to copy it to remote server to run it. screen.sh looks like -

# delete existing screen (could be residual from last test)
for session in $(screen -ls | grep -o '[0-9]\{6\}')
do
    screen -S "${session}" -X quit;
done

screen -d -m -S loadtest; screen -S loadtest -X stuff "cd perftest/s2s/;rm testresult*;./runs2s.sh;"`echo -ne '\015'`;

Herein -
<screen -d -m -S loadtest> creates screen with name “loadtest” and detaches from it

<screen -S loadtest -X stuff> is used to pass subsequent command to screen “loadtest” which we created above

<"cd perftest/s2s/;rm testresult*;./runs2s.sh;C-a d" > does following -
  • navigate to required directory,
  • remove the last test results (my test result files are of format testresult_TimeStamp),
  • ./runs2s runs the load test (that is is running JMeter load test from command line) and
  • `echo -ne '\015'` simulates hitting enter key

but why not create session directly using <screen -s loadtest> and send command to it instead of creating a session, detaching from it and then sending commands to detached session ?
I tried it and failed with the error specified here. Solution specified in the post did not work for me and I had to created a detached screen session and send commands to it.

Why use screen.sh and not send command along with ssh as specified here?
I tried this too, but failed on syntax. There are single and double quotes in screen.sh and escaping did not work. If you are able to send it along with ssh command then please post your comment here.

One test execution is over then I use another ssh loop to bring test results to my machine. Which I merge to one file and begin analysis. ssh loop is pretty simple looks as -

for server in ip1 ip2 ip3;
do
   scp -rp $server:perftest/s2s/testresult.* .
done


That’s all :-)

Popular posts from this blog

Verify email confirmation using Selenium WebDriver

Note: If you are new to java and selenium then start with selenium java training videos .   How to Verify Email Confirmation Using Selenium 4 and JavaMail (2026 Guide) Email confirmation is a critical part of most registration flows — account activation, password reset, multi-factor authentication, and onboarding. Every automation engineer eventually faces the same challenge: How do you verify an email confirmation link inside a Selenium test without making it slow and flaky? The wrong instinct is to automate Gmail's UI with Selenium. It's fragile, slow, and breaks constantly. The right approach: Use Selenium for browser automation Use JavaMail (IMAP) to read the email directly Extract the confirmation link Continue the test in Selenium Why Not Automate Gmail UI With Selenium? Automating the Gmail UI means logging in, searching, clicking a message, and parsing content from a third-party interface that changes frequently. This leads to: Flaky...

Selenium Tutorial: Ant Build for Selenium Java project

Ant is a build tool which could be used to have your tests running either from command line or from Hudson CI tool. There is detailed documentation available for ant here but probably you need to know only a little part of it for you selenium tests. The essentials which are needed to know are: Project Target (ant execution point and collection of tasks) Tasks (could be as simple as compilation) And there would usually be following targets for Selenium tools - setClassPath - so that ant knows where you jar files are loadTestNG - so that you could use testng task in ant and use it to execute testng tests from ant init - created the build file clean - delete the build file compile - compiles the selenium tests run - executes the selenium tests Here is my project set up for ant -

Recording curl request with JMeter Recorder

Just use https://jmeter.apache.org/usermanual/curl.html and no JMeter proxy etc needed : )   Though it is quite east to convert curl requests to corresponding JMeter request. At times you might be stuck with issue like I faced when uploading a file with  JMeter HTTP request In a gist I kept getting 404 error when using REStful service to upload a file. After days of investigations I found it that I should be using HTTP request implementation java and not HttpClient4. JMeter HTTPs Test Script recorder was of great help to debug this issue. This post describes the process of recording curl request through JMeter HTTPs Test Script recorder. If you have never used JMeter HTTPs Test Script recorder then create a new JMeter Plan and under WorkBench > Add > Non Test Element > HTTP(s) Test Script Recorder.  Specify Global Setting > Port as 8090 If we were using browser to record web application then we would configure its proxy to 127.0.0.1 (Since http...