If you're working with JMeter for performance testing and already have a process setup, you are one of the lucky ones. Starting from scratch and getting all of the various parts to fit and work takes time -- too much time especially if you're also involved in functional testing as well.
Aside: If you've stumbled upon this post looking for JMeter advice or a tutorial, please see this JMeter-tips blog. I'll start putting up that once I have anything "post-worthy."
The best processes are what follow the ACEE (pronounced Ace) model: Accurate, Complete, Efficient, and Effective. This means that it should be as automated as possible to take out the human error factor. Granted, a semi-manual JMeter test in GUI mode which produces a log which can then be ported to Excel to generate statistics and fancy graphs can be Accurate, Complete, and Effective -- but it is definitely not as Efficient as executing *ONE* file which does all of that with no other human interaction.
Stay tuned as I explain in following posts one method to get this process implemented. I'll be taking the concepts found from the ProgrammerPlanet-JmeterAntTask and expand on them, so that with one file execution, you will start Performance Monitor with the desired counters, Start JMeter and run the desired tests, Transform the JMeter results into a readable HTML report, Stop Performance Monitor and generate counter metrics and an HTML report, publishing of those HTML reports to a website which can be accessed by anyone on the company network (as the test is completed), Send an email upon successful completion with links to the Jmeter and Perfmon Reports, and finally, Catch and Handle errors by sending an email upon Failure with a log and reason why the test failed.
I'll be referencing the following, so if you are interested in this method, please check them out:
Aside: If you've stumbled upon this post looking for JMeter advice or a tutorial, please see this JMeter-tips blog. I'll start putting up that once I have anything "post-worthy."
The best processes are what follow the ACEE (pronounced Ace) model: Accurate, Complete, Efficient, and Effective. This means that it should be as automated as possible to take out the human error factor. Granted, a semi-manual JMeter test in GUI mode which produces a log which can then be ported to Excel to generate statistics and fancy graphs can be Accurate, Complete, and Effective -- but it is definitely not as Efficient as executing *ONE* file which does all of that with no other human interaction.
Stay tuned as I explain in following posts one method to get this process implemented. I'll be taking the concepts found from the ProgrammerPlanet-JmeterAntTask and expand on them, so that with one file execution, you will start Performance Monitor with the desired counters, Start JMeter and run the desired tests, Transform the JMeter results into a readable HTML report, Stop Performance Monitor and generate counter metrics and an HTML report, publishing of those HTML reports to a website which can be accessed by anyone on the company network (as the test is completed), Send an email upon successful completion with links to the Jmeter and Perfmon Reports, and finally, Catch and Handle errors by sending an email upon Failure with a log and reason why the test failed.
I'll be referencing the following, so if you are interested in this method, please check them out:
You'll also need to be decent with XML, XSLT, HTML, and JavaScript -- so read up on them as well from either W3Schools or Tizag.com.
Part two of the Setup can be found here: http://dudewheysmehblog.blogspot.com/2011/03/jmeter-process-setup-02.html.
Part two of the Setup can be found here: http://dudewheysmehblog.blogspot.com/2011/03/jmeter-process-setup-02.html.
No comments:
Post a Comment