Thursday, 5 March 2015

5. Discussion on Logic Controllers and Its purposes


4. Discussion on Thread Groups


3. Discussion on WorkBench


2. Discussion on Test Plan


1. Discussion on JMeter


JMeter Quiz

Jmeter is used for



Is Jmeter open source software?

Jmeter is not used for



Jmeter does not support



BSF stands for



Select INVALID configuration element in Jmeter.



Jmeter can be used to test performance of



Stress testing is possible by Jmeter?

Select INVALID timer in Jmeter



Which assertion is not used in Jmeter?



Which is the assertion tests where each server response was received within a given amount of time?



Select Status Code for Page not Found Error



Logic Controllers determine


Select INVALID controller in Jmeter



Select controller which makes the user request run specified number of times



Select processor which executes some action before making Sampler Request.


Select testing which uses multiple systems to perform stress testing.



Jmeter supports all the OS supported by Java application

Timer which delays each user request for a random amount of time.



What is a component of Distributed Jmeter Test




Best Practices for your Jmeter Tests

Guidelines to overcome limitations of JMeter in distributed environment:
  1. Limit the Number of Threads
  2. Using a proxy server
  3. Using variables
  4. Reduce resource requirement
  5. Check the JMeter logs
  6. Erase the local path from CSV Data Set Config
  7. Follow file naming convention
JMeter has some limitations especially when it is run in a distributed environment. To use JMeter efficiently for testing, you should use following guidelines:

Limit the Number of Threads

The maximum number of threads you can effectively run with JMeter is 300. This limit is because of hardware's capabilities. If JMeter is made to run with more number of threads, the accuracy of timing information will decrease.

Using a proxy server

The Proxy server helps you to abstract out certain common elements from the recorded samples. Moreover, it is useful features to record your testing.

Using variables

Some test plans need to use different values for different users/threads. For example, you might want to test   a sequence that requires a unique login for each user. This is easy to achieve using variables.

Reduce resource requirement

The GUI mode consumes a lot of computer memory under heavy load. It causes performance issues.
There're some tips to reduce resource requirement:
  • Use non-GUI mode
  • Disable the "View Result Tree" listener during the Load test. Because it consumes more memory and causes JMeter running to run out of memory.
  • Disable all JMeter graphs results
  • Use CSV test result format.
  • Only save the needed test result. JMeter could take a long time to save very detailed test results.

Check the JMeter logs

Any errors in the test plan or test execution will be recorded in the log files. Monitoring the log file help you   to find the error early

Erase the local path from CSV Data Set Config

If you are using an existing CSV data file that you created on your local computer, you should delete the existing local path (Current path of CSV file). If you don't delete the local path, JMeter cannot find the CSV data file on your local PC.

Follow file naming convention

Don't save test plan under complex file name, use only alphanumeric characters.