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
- Version Priority: Automatically selects the highest version when multiple plugins with the same name exist.
- Name Matching: Case-sensitive (
Http
≠HTTP
). - Strong Dependency: Failure to install the corresponding plugin will result in script execution failure.
Supported Plugins
Testing Protocol Plugins
Plugin Name | Description |
---|---|
Http | HTTP protocol testing |
WebSocket | WebSocket protocol testing |
Jdbc | Database connection testing |
Ftp | FTP file transfer testing |
Ldap | LDAP directory service testing |
Mail | Email protocol testing |
Smtp | SMTP email sending testing |
Tcp | TCP network communication testing |
Mock Data Plugins
Plugin Name | Description |
---|---|
MockCsv | Generates CSV-format data. |
MockCustom | Generates custom-format data. |
MockExcel | Generates Excel-format data. |
MockJson | Generates JSON-format data. |
MockSql | Generates Insert SQL-format data. |
MockTab | Generates tab-delimited data. |
MockXml | Generates XML-format data. |
Configuration Example
yaml
# Specify the HTTP protocol testing plugin
plugin: Http
Operations Guide
- Installation Path: Plugins are located in the
${AGENT_HOME}/plugins/
directory of the Agent. - Naming Convention:
xcan-angus.[name]-[type]-plugin-[version].zip
. - 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.