Jmeter assertion, rendezvous, transaction, thinking time, the order of execution

First, in response to the assertion

1. Under what circumstances to use assertions

 Minimize the use of assertions, assertions will affect the performance results for the database insert, modify, delete, and so can not assert, finish the script to check database

2. The assertion method

 Add response assertion

 

 Second, the collection point

1. Rendezvous role

 Set point is generally used to test the instantaneous pressure concurrent

2. Add rendezvous

 

 The number of users group settings, it will perform when it reaches the number of threads together, timeout is 0, the thread does not meet the conditions, will have to wait, timeout is not 0, then wait until the timeout is when the conditions are not met, continue

Third, the transaction

1. Transaction

When the results of the performance tests statistics we will focus on TPS, is the number of transactions per second, JMeter automatically counted as one transaction each request, but sometimes we want to count multiple operations into a transaction, such as sign-on capabilities include two requests . This function may be implemented by a logic controller transaction controller.

2. Add the transaction controller

 

 

 

 Fourth, think time

 1. Think Time

 Thinking time is generally used to simulate real user behavior, but the addition of thinking time, the buildup will reduce the time server request

2. Add a fixed timer

 

 After the addition, the retransmission request requesting the vertical interval of time will be many milliseconds

Fifth, the order of execution

In the same scope, JMeter execution time sequence and add components substantially the same pop-up menu:

　　· Original configuration (Configuration elements)

　　· Pre-Processor (Pre-Processors)

　　• Timer (Timers)

　　· Sampler (Sampler)

　　· Post-processor (Post-Processors)

　　· Assertion (Assertions)

　　· Listener (Listeners)