Thanks Nirodha. Your xsl transformation would be a good addition to improve readability of Jmeter results. However displaying the result on surefire report is the more vital requirement, when test runs on our CI servers, the generated results should be compatible to read by bamboo and display on dashboard. So any possibility to use the same xsl to transport jmeter(*.jtl) to generate surefire report. However we have already done that in different way. Lets try to do use the xsl and improve surefire report in next phase.
Thanks, Krishantha. On Fri, Mar 8, 2013 at 1:57 PM, Nuwan Wimalasekara <[email protected]> wrote: > > > On Fri, Mar 8, 2013 at 1:20 PM, Nirodha Pramod <[email protected]> wrote: > >> Hi Nuwan, >> >> There is an already written xsl transformation to convert the jmeter >> results file (*.jtl) to a comprehensive html report. I have used that for >> generating test reports for one of our customers. It's in >> JmeterHome/extras/jmeter-results-report_21.xsl. Actually there are several >> transformations you can use depending whether you need a detailed report or >> not. I think you can use that or do some modifications to that and use to >> generate reports easliy from the test file. >> > > Thanks Nirodha. will consider this as well > > Thanks, > Nuwanw > >> >> regards, >> Nirodha >> >> >> On Thu, Mar 7, 2013 at 8:43 PM, Nuwan Wimalasekara <[email protected]>wrote: >> >>> >>> >>> On Fri, Mar 8, 2013 at 10:11 AM, Krishantha Samaraweera < >>> [email protected]> wrote: >>> >>>> Hi Nuwan, >>>> >>>> It would be a great idea to write a simple "how to use" doc based on >>>> instructions in this mail. So we can add that to our documentation space. >>>> >>> will work on this. >>> >>>> >>>> Thanks, >>>> Krishantha. >>>> >>>> On Fri, Mar 8, 2013 at 10:06 AM, Nuwan Wimalasekara <[email protected]>wrote: >>>> >>>>> Hi >>>>> We have already added the basic Jmeter reports with the framework .you >>>>> can use surefire reports to find result. if there is a assertion failure >>>>> according to your jmx script It count as a test failure. in addition to >>>>> that, A log file and a report(xml) file are generated for each and every >>>>> script. After running the test, directory called jmeter is generated in >>>>> target directory. There are two directory named logs and reports under >>>>> jmeter directory. in those directory you can find the Jmeter reports and >>>>> logs for each script. The log file and report file names will be you test >>>>> script name + time stamp >>>>> >>>>> Thanks, >>>>> Nuwanw >>>>> >>>>> >>>>> On Thu, Mar 7, 2013 at 11:12 PM, Lalaji Sureshika <[email protected]>wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> This will be really value added feature to evolve product integration >>>>>> tests.Specially in APIManager,we have used several jmeter test scripts >>>>>> time >>>>>> to time,to test product functionality with help of QA team.. >>>>>> >>>>>> One question,how the results of executed jmeter scripts with >>>>>> integration tests output..?Will it generate reports per each jmeter test >>>>>> case? >>>>>> >>>>>> >>>>>> Thanks; >>>>>> >>>>>> On Thu, Mar 7, 2013 at 6:42 PM, Nuwan Wimalasekara >>>>>> <[email protected]>wrote: >>>>>> >>>>>>> Hi all, >>>>>>> We have enable the test automation framework to run Jmeter script >>>>>>> alone with integration test while building products. There are lot of >>>>>>> Jmeter script for product functional testing and those are >>>>>>> manually triggered from Jmeter tool after building the product to test >>>>>>> product functionality. with this feature you can execute the Jmeter test >>>>>>> which ensure a functionality of a product with proper assertions with >>>>>>> the >>>>>>> product integration test and see the test reports. >>>>>>> >>>>>>> if you have any Jmeter script(.jmx) file, Please integrate those >>>>>>> test with the integration test. Please send the feedback if you face >>>>>>> any >>>>>>> limitation or issue while integrating. >>>>>>> >>>>>>> Please find the source code from[1] >>>>>>> >>>>>>> Note : This is not recommended for load testing with high value. >>>>>>> >>>>>>> You need to have bellow dependency >>>>>>> <dependency> >>>>>>> <groupId>org.wso2.carbon.automation</groupId> >>>>>>> >>>>>>> <artifactId>org.wso2.carbon.automation.tools.jmeter</artifactId> >>>>>>> <version>4.0.8</version> >>>>>>> </dependency> >>>>>>> >>>>>>> Then you can write a test method in your integration test to run >>>>>>> Jmeter script. >>>>>>> >>>>>>> @Test() >>>>>>> public void serviceListTest() throws Exception { >>>>>>> JMeterTestManager test = new JMeterTestManager(); >>>>>>> JMeterTest file = new JMeterTest(new >>>>>>> File("$PATH/ESB-list-service.jmx")); >>>>>>> test.runTest(file); >>>>>>> } >>>>>>> >>>>>>> [1] >>>>>>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/platform-integration/clarity-framework/4.0.8/org.wso2.carbon.automation.tools.jmeter/ >>>>>>> >>>>>>> Thanks >>>>>>> Nuwanw >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Nuwan Wimalasekara >>>>>>> Software Engineer - Test Automation >>>>>>> WSO2, Inc.: http://wso2.com >>>>>>> lean. enterprise. middleware >>>>>>> >>>>>>> phone: +94 71 668 4620 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Dev mailing list >>>>>>> [email protected] >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Lalaji Sureshika >>>>>> Software Engineer; Development Technologies Team;WSO2, Inc.; >>>>>> http://wso2.com/ >>>>>> email: [email protected]; cell: +94 71 608 6811 >>>>>> blog: http://lalajisureshika.blogspot.com >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Nuwan Wimalasekara >>>>> Software Engineer - Test Automation >>>>> WSO2, Inc.: http://wso2.com >>>>> lean. enterprise. middleware >>>>> >>>>> phone: +94 71 668 4620 >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>> >>> >>> -- >>> Nuwan Wimalasekara >>> Software Engineer - Test Automation >>> WSO2, Inc.: http://wso2.com >>> lean. enterprise. middleware >>> >>> phone: +94 71 668 4620 >>> >>> >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Nirodha Gallage* >> Software Engineer, QA. >> WSO2 Inc.: http://wso2.com/ >> Email: [email protected] Mobile: +94716429078 >> > > > > -- > Nuwan Wimalasekara > Software Engineer - Test Automation > WSO2, Inc.: http://wso2.com > lean. enterprise. middleware > > phone: +94 71 668 4620 > > > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
