When i select any class and testmethod as Junit 4 test case, it disapears as soon as i click something else and a default test case comes up that gives me a null exception,for eg: groovy test case/Selenese Test Case. I require the Groovy Library for my test case.
This happens only in Jmeter 2.13, but this unchecking thing does not happen in Jmeter 2.11, but i need to use the Backend Listener that is only in Jmeter 2.13.
Image that shows the selection of the junit testcase
Image that shows that the test selected is rechecked by some default groovy test case/Selenese Test case
Screenshot of jmeter using Nightly Build
I need a solution to this, please help me out. Thank you
It appears you are facing a NPE in a process related to undo/redo feature:
https://github.com/apache/jmeter/blob/v2_13/src/core/org/apache/jmeter/gui/GuiPackage.java#L853
Could you try to remove jmeter-plugins 1.4.0 which is a developer snapshot.
Try without it, and if it works report a bug to jmeter-plugins.org
Then try with jmeter-plugins-1.3.1 which is the stable version, it might work but the bug might also be in it.
I created bug:
- https://bz.apache.org/bugzilla/show_bug.cgi?id=58795
It is now fixed in nightly build so you will have more informations to provide to jmeter-plugins or jmeter.
To use nightly build:
http://jmeter.apache.org/nightly.html
Download the _bin and _lib files
Unpack the archives into the same directory structure
The other archives are not needed to run JMeter.
Related
I'm using Cypress to run a suite of automated tests.
The current version of cypress provides mocha-junit-reporter out of the box, and provides configuration options to pass to the reporter. One of the options is the 'mochaFile'.
I'm using the recommended [hash] tag to output reports across multiple spec files.
this results in a flat mess of files that look like 'results/test-output-abc12345.xml'.
What I want instead is for the test file's relative path and filename to be pass in as the reporter's output file path.
This would give me a structured, feature first view of the output, and in Azure Dev Ops, which aggregates the test output, it would give me correct filenames to detect intermittently failing tests.
Things I've tried that haven't worked:
I've tried to use hooks to modify Cypress's config or set environment variables to try to override the reporterOptions/mochaFile per test at (hopefully) the right time.
I've tried to grab the outputted defaultly-named xml file, and copy it to the correct path+filename given the Cypress.spec.name context, but I can't seem to find the right hook or time to do this.
after and afterEach don't work - I don't think the test report has saved the file yet.
Using a plugin, hooking to some event on test:before:run or test:after:run seem promising, but I'm flying blind since I can't debug into it, so I've been unsucessful in modifying the reporter's output path or copying the file.
I'd love it if someone could show a working example using mocha-junit-reporter, or even a different mocha compatible reporter, if the reporter would play well with Azure Dev Ops, and can help me discover intermittently failing tests.
I have an ASP .NET MVC project that is built in a Jenkins project. We're using the nUnit plugin to fangle the output from our unit tests as a post-build step.
I've just added Jasmine tests for the javascript in the project and added a step in MSBuild to have Chutzpah run the Jasmine tests and output the results in jUnit format.
I added a post build step to process the jUnit results file and Jenkins runs the build and presents two 'Test Results' links in the Build result page...
However, when I click those links both go to the same result. When I left yesterday it was the nUnit results this morning it's the jUnit results so I'm guessing that it's just whichever finished last?
Is this possible? Do I need to do things a different way?
I would try just using the xUnit plugin, that way you can configure it to take bothe the junit and nunit test results all in a single publisher.
There is a bug in Jenkins related to this: NUnit Plugin fails to merge Unit test reports with unit tests split on basis of category.
To get around this, just put your NUnit post build action as the last that it works!
I was trying to integrate my cucumber tests with maven-cucumber-reporting(from masterthought.net). I downloaded their Jenkins plugin and incorporated in my pom.xml file.
I have 2 tests in my eclipse project and when I ran these tests though maven it gets executed successfully. But, when I see my HTML report and also the cucumber.json , it displays details of only one test case.
I have been using Cucumber-JVM
Can you please let me know if I'm going wrong somewhere.
Thanks,
Prashanth
Do you have two RunCukesTest files for your two tests? If so make sure that you are creating unique json files for each tests (Note Test1.json below, make sure you have that distinction for each of your tests). Otherwise they will be overwritten by each other and you will only see the results from your last test.
#Cucumber.Options(format = { "pretty", "html:target/cucumber-html-report",
"json-pretty:target/Test1.json" },
features = { "src/test/resources/features" })
I've put together a custom JUnit runner that saves a screenshot when a WebDriver test fails.
I'm using Maven's failsafe plugin to create reports of the integration tests and TeamCity is our CI server.
I know TeamCity supports custom reports, but I don't know how I'd embed the image files into an HTML page (or pages) with references to the relevant tests.
What would be a good method to integrate the screenshots into the test report?
Is there a Maven plugin that'll do the job?
Maybe Allure-report would suit for your purpose. It allows to create a nice report that contains different attachments, including screenshots. Moreover it has JUnit integration and Teamcity plugin, so it fully covers your use-case.
Unfortunately there is no way to simply change the reports cause they are generated by the maven-report-plugin which can't be simply changed.
What you can try is to create a separate folder and create a link via the site.xml descriptor.
You can try maven-cobertura-plugin. Including this in your build will generate a HTML report of all the test case success, failure and coverage. Hope this helps....
we need to do some integration testing of some Java classes which we want to run inside a Weblogic server. We have a JUnit test suite that runs a set of Junit test classes, and I would like to know if is a good idea to write a JSP that runs the test suite and prints out the results in a graphical way, in case we won't be able to access via SSH to the server and run the tests via console.
Step 1: We upload the jar file with the tests and the JSP
Step 2: We call the JSP via a browser
Step 3: Profit! Our tests are running and we have visual feedback.
Am I right or wrong? Thanks for your advices!
You should be able to use Cactus to do this,
See the following article for reference:
http://www.oracle.com/technetwork/articles/server-side-unit-tests-096611.html
That should save you having to write extra code, not sure about visual feedback but the Cactus page seems to suggest that when running in a servlet container like Tomcat you should get the results visually:
http://jakarta.apache.org/cactus/integration/howto_tomcat.html