How to properly configure Jenkins to display Jmeter tests? - jenkins

guys!
I'm running some jmeter tests on Jenkins, and for some reason it stops displaying the results of the last test run and freezes, only displaying results from a run that has been completed berofe, for example, if I start a new run, it will display the results from a previus one over and over again, no matter how many times I run the test suit... Is it any config that I need to change?
Thanks!

I'm using the performance plugin... I was analysing it a bit more and I found out that if a test fails once, this failure will be displayed everytime I run a new test and it's displayed as a failed build by jenkins... In the image, the failed test contains two outputs in the http code, 200 which stands for success and 500 which stands for failed (I believe i'm right).

Related

JMeter + Jenkins - How to view Response Data/Assert Failed Results using Performance Plugin in Jenkins

I am integrating JMeter to Jenkins and displaying the result/report using the Performance Plugin and so far it is working fine when the the report shows the Info about if the request is successful or failed, how much time does it take, percentage of error...
I would like to display here more Info if the request is failed, such as Response Data, or in case if it is failed because of an assertion, it should display the message here. Saying in other words, these approaches should act same as View Results Tree Listener in JMeter GUI but I do not know how to attach it to the Performance Plugin in Jenkins.
Does anyone have an idea how to achieve it? Thank you in advanced!
What you can do it add to your plan a View Results Tree and:
fill in file name property.
Click on Configure and check everything except CSV Column Names
Set Errors only
This way, when an error occurs, you'll have all details in this XML file which you can load in JMeter after test to analyze errors.

TFS 2015 test case outcome = "None"

I'm using TFS 2015 to run automated regression tests nightly. There are over 100 tests in the suite but each night 1 of them, usually the same one, shows up with the outcome "None".
If I look at the test log I see that the test does not fail. If I remove this test from the suite then on the next run the test above that one, in code, will show as "None" but it also passes.
What could cause this and how do I determine the cause?
We upload results after finishing execution of the set of tests given
to an agent. From #1410 it sounded like all your tests are
currently going to 1 machine, which would mean all results are
uploaded only at the end. Also, the Test Results tab in Build Summary
(image you pasted above) only shows results once the run is complete.
You can go to the Runs tab in the Test Hub to see test results as and
when they are available, even for in progress runs (image below)
Source Link
So in other words, you have to wait for the full completion of the process, the root cause of the status none issue maybe either your enitre test process haven't finished yet or something special cause the process not finished.

how to show quantitative results in Jenkins

Jenkins test results screen shows only pass/failed results.
I would like to show quantitive (number/percentage/time duration etc') results, parsed from logs.
e.g. memory usage, run time of specific methods etc..
What is the best way to do so?
Thanks
good question.
i imagine you're probably looking to extend your Jenkins instance with some plugins that describe more info about the tests you've run. this plugin seems relevant, but requires some experience with JMeter (java-based performance measurment tool) to generate the output that this plugin can then read and display output from a JMeter task that you can run every time your build runs:
https://wiki.jenkins-ci.org/display/JENKINS/Performance+Plugin
the 'readme' in the above plugin details page specifies how to set up a project to run JMeter( see the 'Configuring a project to run jmeter performance test:' near the bottom.
another way to do similar not so immediately tied to a specific jenkins build is to run resource monitors (like Cacti or collectd) on the machines running the tests and analyze those results post-build, but again, outside of the Jenkins context.
HTH.

HTTP access to on-going Jenkins build files

I guess the title is pretty self-explanatory. The reason I want that is so that I can make a live custom HTML reporter for my tests.
My test suite takes hours to complete, and although the tests generate HTML reports as soon as each test step is executed, it's only at post-build time that those report files get published.
Being able to see them as they get generated would reduce the time it takes for me and my teammates to analyze and act upon issues revealed by our test runs.
All I need is that Jenkins let me access the build files as the build executes. Nothing fancy; I can take care of the rest. Is that possible? How?
In our setup there is always an intermediate file (typically XML) but the HTML files are created at the end of the job.
What you can do, is use the progressive output (http://jenkins/job/jobName/buildNumber/logText/progressiveText?start=0). Although you don't state which framework you use, most of them output something that would be easy to parse. e.g. "Test xxx failed".

configure grid extra (groupon) with jenkins in order to run cucumber tests

I'm struggling with something for quite a while and can't find a solution,
I got a test project (cucumber, maven) I configure jenkins to pull the project from github, build and execute the code (selenium test script) on jenkins slave and that works perfect, I added few more slave, tagged them and I'm able to execute the same job parallel(the same test cases on different machines)
my next step is to use grid extra (https://github.com/groupon/Selenium-Grid-Extras) in order to use some cool features like video recording, browser updating, selenium updates etc...
now, I know that in order to use the grid I need to address it via my code and also define the desired capabilities (browser, os etc...).
currently when I'm running the same job twice, my second request will be queued till the first one ends, if I will run the same code from two developers machine it will run at 2 different nodes and the grid can handle both request.
not sure what is wrong with my jenkins configuration or my grid hub configuration, I checked it again and again and all looks good :-)
so guess I'm missing something
any advice/direction/idea will be highly appreciated.
Thanks
Ronen

Resources