Jmeter tutorial on Jmeter components, terminologies etc…
1. Thread group – refers the virtual users count applied while performance testing using Jmeter.
How we design the user transactions or thread group?
1) The requirement is given that 60 user transactions needs to be made. And requested for 3 sec interval between transactions
2) Then Ram up time should be set 180 sec. This will fulfill the requirement of 3 sec delay between transactions
3) This will also ensure that the 60th thread or user will be starting the action at 180th sec. ( i.e Ramp up time / number of users – will give you the time interval for each uses to kick off. Total ramp up time will be the total time to start all transactions including the 60th one. Based on the transaction scenario length probably first set of 1 to 50th ones may be finished by this time) – similar articles on Jmeter , script Recording
2. Samplers
Samplers are transaction makers which will let you send transactions.
For e.g HTTP Request sampler is used, it will send HTTP/HTTPS request to the web server. This requests can be manually added or recorded using HTTP(S) Test Script Recorder.
Web embedded resources like CSS, images, java applets, scripts, background images are retrieved by HTTP requests.
similar article on Jmeter
3. Test plan
Test plan is the container of all the performance test scenarios and components of the particular test in Jmeter. Test plan consists of Thread group , temporary work bench, Samplers, etc.