JMeter execution does not stops when using WebDriver - selenium-webdriver

I'm using latest JMeter 3.3 to run a latest Selenium WebDriver test, everything seems to be OK,
I only have 1 thread configured with 1 sec ramp up and 1 loop count, however after the webdriver execution is completed, JMeter does not stops the overall test execution and keeps on executing the test for infinity, I'm not sure why is that happening, I'm using chromedriver and all the configuration I have done is as per jmeter documentation, I have also added WDS.sampleResult.sampleEnd() command at the end of my script. Please refer screenshots attached -
Thread Group -
I just want as soon as my sample ends, JMeter test execution should also stop.

There is a problem in your configuration as per the bug report you made:
https://bz.apache.org/bugzilla/show_bug.cgi?id=61661
You have the below exception occurring which is due to missing jar that contains:
com/sun/jna/platform/win32/Kernel32
So download it with it dependencies put it in jmeter/lib folder.
You can find it here:
http://www.java2s.com/Code/Jar/j/Downloadjna330platformjar.htm
http://www.java2s.com/Code/Jar/j/Downloadjna330jar.htm

Related

JMeter - non GUI mode - how to get the app to run continously

I can get JMeter to run in non GUI mode but it stops after just running just one iteration. How do I get it to run continuously ? Loop Count is set to Infinite in this 5.5 JMeter version.
jmeter -n -t SocialGeneratorTrafficMOCKSQS.jmx -l C:\installs\How2Run_JMeter5_5_cmd_line\Results.csv -e -o C:\installs\How2Run_JMeter5_5_cmd_line\Report.csv
thank you
The reason for stopping the thread can be found in jmeter.log file
I can think of 2 possible reasons which might cause premature ending of your test:
CSV Data Set Config is configured to stop thread on EOF, make sure it's set up like at the image below:
Flow Control Action sampler is configured to stop either thread or test

Once completing the thread the count down timer still working.. why is that?

I have used 100 users for my testing and it is completed 100 and it shows as 100/100 in the right-hand upper corner, but the timer is working? I don't know why is that..can you please explain to me why it happens like that. because when am using 5 users and once it completed timer is stopped. please help me. please check the attachment.
There is no any attachment however I can try to guess the possible reason.
When you start JMeter the following beautiful warning is displayed:
================================================================================
Don't use GUI mode for load testing !, only for Test creation and Test debugging.
For load testing, use CLI Mode (was NON GUI):
jmeter -n -t [jmx file] -l [results file] -e -o [Path to web report folder]
& increase Java Heap to meet your test requirements:
Modify current env variable HEAP="-Xms1g -Xmx1g -XX:MaxMetaspaceSize=256m" in the jmeter batch file
Check : https://jmeter.apache.org/usermanual/best-practices.html
================================================================================
So my expectation is that 100 users is way too much than JMeter GUI can handle so consider running your JMeter test in command-line non-GUI mode and it should end normally/gracefully. If it doesn't - make sure to follow JMeter Best Practices

PhpUnit runs indefinitely

None of the PHP Unit tests implemented run.
It doesn't throw errors either.
No errors are logged and the test keeps running infinitely.
C:\xampp_v7.0\htdocs\...>vendor\bin\phpunit --verbose tests\TestCase\Model\Table\UsersTableTest.php
PHPUnit 6.5.9 by Sebastian Bergmann and contributors.
Runtime: PHP 7.0.30 with Xdebug 2.5.5
Configuration: C:\xampp_v7.0\htdocs\...\phpunit.xml.dist
I restarted MySql server and this was fixed.
Another possible reason could be
Errors in the data loaded in Fixtures (Any syntax errors in the fixture files can lead to this situation) This can be identified by excluding all fixtures and including them one at a time and running the tests. Using this way the fixture that caused the issue can be found.

Android build fails in codenameone build sever

My android build fails after build and this is the error log i get
Total time: 1 mins 16.631 secs
Stopped 0 compiler daemon(s).
Received result Failure[value=org.gradle.initialization.ReportedException: org.gradle.internal.exceptions.LocationAwareException: Execution failed for task ':dexRelease'.] from daemon DaemonInfo{pid=5907, address=[10331ba5-2501-41cc-aa13-52a0ba46bd51 port:41817, addresses:[/0:0:0:0:0:0:0:1%1, /127.0.0.1]], idle=false, context=DefaultDaemonContext[uid=2862cb6d-50e8-4321-a1fa-590435e89f0f,javaHome=/usr/java/jdk1.7.0_67,daemonRegistryDir=/home/ec2-user/.gradle/daemon,pid=5907,idleTimeout=120000,daemonOpts=-XX:MaxPermSize=512m,-XX:+HeapDumpOnOutOfMemoryError,-Xmx1500m,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant]} (build should be done).
This is probably related to this: https://www.codenameone.com/blog/video-new-defaults-barcode-qrcode-changes.html
You can workaround this by using android.gradle=false in the build hints. However, I'm guessing its related to some cn1lib or build hint you added. But it seems the build error log you provided is partial so I don't see any issue there.

parallel builds in jenkins

I just installed the "Build Flow" plugin ver 0.7 and i seem to have issues getting it to work. I configured 2 simple jobs (JOB1 and JOB2). Then another jenkins job which i named "parallel_build} that basically calls this job to build them in parallel.
In the "Define build flow using flow DS" section i have the following
parallel ( {buildIJOB1)}, {build(JOB2)} )
when i execute "parallel_build" job, the console output print the following msg and return a build faillure
parallel {
}
Notifying upstream projects of job completion
Finished: FAILURE
It does not seem to be executing the jobs i intend to run in parallel. The two jobs (JOB1 and JOB2 are pretty simple. All they do is print hello msg.
I appreciate any help in advance.
Jenny
Never mind folks. Upgrading to the latest jenkins version (1.501) from 1.447 fixed the issue. It's all good now.
try this syntax
parallel(
{build("JOB1")},
{build("JOB2")}
)

Resources