Skip to content

Plugin Configuration

Plugins are used to specify the runtime environment required for script execution. The system will automatically select the highest version of the plugin with the same name for execution.

Plugin Selection Rules

  1. Version Priority: Automatically selects the highest version when multiple plugins with the same name exist.
  2. Name Matching: Case-sensitive (HttpHTTP).
  3. Strong Dependency: Failure to install the corresponding plugin will result in script execution failure.

Supported Plugins

Testing Protocol Plugins

Plugin NameDescription
HttpHTTP protocol testing
WebSocketWebSocket protocol testing
JdbcDatabase connection testing
FtpFTP file transfer testing
LdapLDAP directory service testing
MailEmail protocol testing
SmtpSMTP email sending testing
TcpTCP network communication testing

Mock Data Plugins

Plugin NameDescription
MockCsvGenerates CSV-format data.
MockCustomGenerates custom-format data.
MockExcelGenerates Excel-format data.
MockJsonGenerates JSON-format data.
MockSqlGenerates Insert SQL-format data.
MockTabGenerates tab-delimited data.
MockXmlGenerates XML-format data.

Configuration Example

yaml
# Specify the HTTP protocol testing plugin  
plugin: Http

Operations Guide

  1. Installation Path: Plugins are located in the ${AGENT_HOME}/plugins/ directory of the Agent.
  2. Naming Convention: xcan-angus.[name]-[type]-plugin-[version].zip.
  3. Version Update: Replace the plugin file in the directory to upgrade.

💡 Tip: Before execution, verify via the Agent console that the target plugin is installed and meets version requirements.

Released under the GPL-3.0 License.