The Test Plan is where the overall settings for a test are specified
- Name: Generally we give project name like “Orange Hrm”
- Comments: Give brief description about this project. it increases the readability of this template (Test Plan).
- User Defined Variable:Static variables can be defined for values that are repeated throughout a test.
- Example - Name :serverip and value :opensource.demo.orangehrm.com
Here we can access application by using ${serverip} throughout a test plan.
Details - It shows the details information of selected variable in popup window.
Add: It allows us to add new user defined variable.
Add from clipboard - it allows us to add values from clipboard (copy and paste)
Delete - Selected user defined variable will be deleted.
Up and Down - it allows us to manage the order of variables. it can move the positions of variables.
- Run thread groups consecutively(Selected) :To run the no of Thread Group serially(one after once) rather than in executing parallelly.( Generally we use it while debugging script in suite level.)
- Run tearDown Thread Groups after shutdown of main threads: if selected, the tearDown groups (if any) will be run after graceful shutdown of the main threads. The tearDown threads won't be run if the test is forcibly stopped.
- Functional Test Mode: JMeter to save the additional sample information - Response Data and Sampler Data - to all result files. This increases the resources needed to run a test, and may adversely impact JMeter performance. If more data is required for a particular sampler only, then add a Listener to it, and configure the fields as required. [The option does not affect CSV result files, which cannot currently store such information.]
- Add directory or jar to classpath:Test plan now provides an easy way to add classpath setting to a specific test plan. However it can be useful for utility jars such as JDBC drivers and additional plugins. The jars are only added to the search path for the JMeter loader, not for the system class loader.
