Constructor Detail

• LoginConfigGui

  LoginConfigGui()

  Create a new LoginConfigGui as a standalone component.

• LoginConfigGui

  LoginConfigGui(boolean displayName)

  Create a new LoginConfigGui as either a standalone or an embedded component.

  Parameters:

  displayName - indicates whether or not this component should display its name.

Method Detail

• getLabelResource

   String getLabelResource()

  Get the component's resource name, which getStaticLabel uses to derive the component's label in the local language. The resource name is fixed, and does not vary with the selected language.

  Normally this method should be overridden in preference to overriding getStaticLabel(). However where the resource name is not available or required, getStaticLabel() may be overridden instead.

  Returns:

  the resource name

• configure

   void configure(TestElement element)

  A newly created component can be initialized with the contents of a Test Element object by calling this method. The component is responsible for querying the Test Element object for the relevant information to display in its GUI.

  Parameters:

  element - the TestElement to configure

• createTestElement

   TestElement createTestElement()

  JMeter test components are separated into a model and a GUI representation. The model holds the data and the GUI displays it. The GUI class is responsible for knowing how to create and initialize with data the model class that it knows how to display, and this method is called when new test elements are created.

  Since 5.6.3, the default implementation is as follows, and subclasses should override makeTestElement

  public TestElement createTestElement() {
      TestElement element = makeTestElement();
      assignDefaultValues(element);
      return el;
  }
  

  Before 5.6.3 the canonical implementation was as follows, however, it is recommended to avoid overriding createTestElement and override makeTestElement instead.

  public TestElement createTestElement() {
      TestElementXYZ el = new TestElementXYZ();
      modifyTestElement(el);
      return el;
  }
  

  Returns:

  the Test Element object that the GUI component represents.

• modifyTestElement

   void modifyTestElement(TestElement element)

  GUI components are responsible for populating TestElements they create with the data currently held in the GUI components. This method should overwrite whatever data is currently in the TestElement as it is called after a user has filled out the form elements in the gui with new information.

  If you override AbstractJMeterGuiComponent, you might want using bindingGroup instead of overriding modifyTestElement.

  The canonical implementation looks like this:

  @Override
  public void modifyTestElement(TestElement element) {
      super.modifyTestElement(element); // clear the element and assign basic fields like name, gui class, test class
      // Using the element setters (preferred):
      // If the field is empty, you probably want to remove the property instead of storing an empty string
      // See Streamline binding of UI elements to TestElement properties
      // for more details
      TestElementXYZ xyz = (TestElementXYZ) element;
      xyz.setState(StringUtils.defaultIfEmpty(guiState.getText(), null));
      xyz.setCode(StringUtils.defaultIfEmpty(guiCode.getText(), null));
      ... other GUI fields ...
      // or directly (do not use unless there is no setter for the field):
      element.setProperty(TestElementXYZ.STATE, StringUtils.defaultIfEmpty(guiState.getText(), null))
      element.setProperty(TestElementXYZ.CODE, StringUtils.defaultIfEmpty(guiCode.getText(), null))
      ... other GUI fields ...
  }
  

  Parameters:

  element - the TestElement to modify

• clearGui

   void clearGui()

  Implements JMeterGUIComponent.clearGui