Posts

Showing posts with the label Non-Functional-Test

Tips of Load Test Meetup with SkiPjaQ

{ how often you run test, how often code change, audience changes. } { LATENCY, CONCURRENT USER } { DESCRIPTIVE model,  study the user behavior and design test accordingly. Do not random. } { design waiting time in the test to avoid saturation, production data arbitrary command, run queue length } { report: [Jmeter + influx db, use thread and wait time to get a optimized ration, no aggregate report enabled, find the deritive of the cure.] }

Performance Test in DevOps

Image
Model -> Test Interesting Change Things is smaller and smaller ​

SoapUI Load Test explain

Thread : number of user Test delay : delay between each run to simulate a breathing space for the server. Random: delay will be random between [random * give delay : given delay]

JMeter Listener and how to use JMeter.

NEVER run a load test on the JMeter GUI! Use it only for test recording, development, and debugging. NEVER run a load test on the JMeter GUI! Use it only for test recording, development, and debugging. JMeter  listeners enables performance engineers to monitor the requests sent from JMeter as well as to analyze the responses received from the system under test.  Nearly all listeners have the ability to write results to a file, allowing performance engineers to transform them to the format they need for analysis. View Results Tree  listener provides the request parameters, response parameters and the response data. The  Simple Data Writer  is such a listener. This listener can write results only to the filename that is provided.  All listeners can be found by right clicking the test plan  Add  >  Listeners . A  JMeter  listener will only collect data from JMeter elements at or above its level. The Agg...