JaVa
   

Summary

In this chapter, we discussed testing our Web app with JMeter. We used JMeter to test the front end of the pet store: the navigation. And, we used JMeter to test the back end of the pet store: the product management piece to add, delete, and edit products. We also set up a test to work with JDBC testing. Because JMeter makes performance testing so easy, you won't do what some developers do—you won't wait until the end of the project to measure performance. You can now incrementally build tracer bullets of the system and measure performance of the tracer bullets. You can identify major bottlenecks before they become the overriding architecture for your system. To use JMeter, you must construct and run a TestPlan that consists of one to many ThreadGroups. A thread is like a simulated user. JMeter forms a JMeterEngine from the TestPlan. Then, the JMeterEngine creates threads, and each thread iterates through the test cases that you set up. The test cases are stored in simple XML.

You can use JMeter to post and get pages. You can also send HTML parameters to simulate a form post. Sometimes you may want to manage the session information cookie with a JMeter cookie manager. We needed to do this to navigate to the Product page of the pet store, because the current subcategory was stored in the session information.


JaVa
   
Comments