Package org.apache.jmeter.config
Class ConfigTestElement
java.lang.Object
org.apache.jmeter.testelement.AbstractTestElement
org.apache.jmeter.config.ConfigTestElement
- All Implemented Interfaces:
- Serializable,- Cloneable,- ConfigElement,- Searchable,- org.apache.jmeter.testelement.TestElement
- Direct Known Subclasses:
- Arguments,- AuthManager,- CacheManager,- CookieManager,- CSVDataSet,- DNSCacheManager,- HeaderManager,- HTTPFileArgs,- JavaConfig,- KeystoreConfig,- LDAPArguments,- LoginConfig,- MongoSourceElement,- RandomVariableConfig
- See Also:
- 
Nested Class SummaryNested classes/interfaces inherited from interface org.apache.jmeter.testelement.TestElementorg.apache.jmeter.testelement.TestElement.Companion
- 
Field SummaryFieldsFields inherited from interface org.apache.jmeter.testelement.TestElementCOMMENTS, Companion, ENABLED, GUI_CLASS, NAME, TEST_CLASS
- 
Constructor SummaryConstructors
- 
Method SummaryModifier and TypeMethodDescriptionvoidaddConfigElement(ConfigElement config) Add a configuration element to this one.voidaddTestElement(org.apache.jmeter.testelement.TestElement parm1) booleanIf your config element expects to be modified in the process of a test run, and you want those modifications to carry over from sample to sample (as in a cookie manager - you want to save all cookies that get set throughout the test), then return true for this method.org.apache.jmeter.testelement.schema.PropertiesAccessor<? extends ConfigTestElement,? extends org.apache.jmeter.config.ConfigTestElementSchema> getProps()org.apache.jmeter.config.ConfigTestElementSchemaMethods inherited from class org.apache.jmeter.testelement.AbstractTestElementaddPropertiesValues, addProperty, addProperty, canRemove, clear, clearTemporary, clearTestElementChildren, clone, emptyTemporary, equals, getComment, getName, getProperty, getPropertyAsBoolean, getPropertyAsBoolean, getPropertyAsDouble, getPropertyAsFloat, getPropertyAsInt, getPropertyAsInt, getPropertyAsLong, getPropertyAsLong, getPropertyAsString, getPropertyAsString, getPropertyOrNull, getSearchableTokens, getThreadContext, getThreadName, hashCode, isEnabled, isRunningVersion, isTemporary, logProperties, mergeIn, propertyIterator, recoverRunningVersion, removeProperty, setComment, setEnabled, setName, setProperty, setProperty, setProperty, setProperty, setProperty, setProperty, setProperty, setProperty, setProperty, setRunningVersion, setTemporary, setThreadContext, setThreadName, traverse, traverseCollection, traverseMap, traversePropertyMethods inherited from class java.lang.Objectfinalize, getClass, notify, notifyAll, toString, wait, wait, waitMethods inherited from interface org.apache.jmeter.config.ConfigElementcloneMethods inherited from interface org.apache.jmeter.testelement.TestElementget, get, get, get, get, get, get, get, get, getOrCreate, getOrCreate, getOrNull, getOrNull, getOrNull, getPropertyOrNull, getString, removed, removeProperty, set, set, set, set, set, set, set, set, set
- 
Field Details- 
USERNAME- See Also:
 
- 
PASSWORD- See Also:
 
 
- 
- 
Constructor Details- 
ConfigTestElementpublic ConfigTestElement()
 
- 
- 
Method Details- 
getSchemapublic org.apache.jmeter.config.ConfigTestElementSchema getSchema()- Specified by:
- getSchemain interface- org.apache.jmeter.testelement.TestElement
 
- 
getPropspublic org.apache.jmeter.testelement.schema.PropertiesAccessor<? extends ConfigTestElement,? extends org.apache.jmeter.config.ConfigTestElementSchema> getProps()- Specified by:
- getPropsin interface- org.apache.jmeter.testelement.TestElement
 
- 
addTestElementpublic void addTestElement(org.apache.jmeter.testelement.TestElement parm1) Description copied from class:AbstractTestElement- Specified by:
- addTestElementin interface- org.apache.jmeter.testelement.TestElement
- Overrides:
- addTestElementin class- AbstractTestElement
 
- 
addConfigElementAdd a configuration element to this one. This allows config elements to combine and give a "layered" effect. For example, HTTPConfigElements have properties for domain, path, method, and parameters. If element A has everything filled in, but null for domain, and element B is added, which has only domain filled in, then after adding B to A, A will have the domain from B. If A already had a domain, then the correct behavior is for A to ignore the addition of element B.- Specified by:
- addConfigElementin interface- ConfigElement
- Parameters:
- config- the element to be added to this ConfigElement
 
- 
expectsModificationpublic boolean expectsModification()If your config element expects to be modified in the process of a test run, and you want those modifications to carry over from sample to sample (as in a cookie manager - you want to save all cookies that get set throughout the test), then return true for this method. Your config element will not be cloned for each sample. If your config elements are more static in nature, return false. If in doubt, return false.- Specified by:
- expectsModificationin interface- ConfigElement
- Returns:
- true if the element expects to be modified over the course of a test run
 
 
-