Difference between revisions of "WISE-Agent Verification Tool"
(Created page with "'''AgentTester – a software tool for testing all sorts of functions and modules of the Agent.''' == Architecture == The architecture of AgentTester is described as follo...") |
|||
(2 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
+ | == Introduction == | ||
+ | |||
'''AgentTester – a software tool for testing all sorts of functions and modules of the Agent.''' | '''AgentTester – a software tool for testing all sorts of functions and modules of the Agent.''' | ||
+ | == Architecture == | ||
+ | |||
+ | The architecture of AgentTester is described as follows. The agent includes three different layers: Main, Module and Library. | ||
+ | |||
+ | | ||
+ | |||
+ | *'''Main Layer''' | ||
+ | |||
+ | The main executable function to load all the modules required to test functions of an agent. | ||
+ | |||
+ | *'''Module Layer:''' | ||
+ | |||
+ | All modules used to test functions of an agent. | ||
+ | *'''Library Layer:''' | ||
− | == | + | All libraries required in modules. |
+ | |||
+ | [[File:AgentTester.png|760x600px|Architecture of AgentTester]] | ||
+ | |||
+ | | ||
+ | |||
+ | == Configuration == | ||
+ | |||
+ | AgentTester takes an INI file (CheckerSetting.ini) as its configuration to know which modules are required to test an agent according to a user’s requirements. User can modify INI file to load or unload modules for meeting his/her wanted test conditions. | ||
+ | |||
+ | | ||
+ | |||
+ | *''' Modules Section''' | ||
+ | |||
+ | This section is used to define how many and which modules required to load. And the required operation time for the module. | ||
+ | |||
+ | *'''Server Section''' | ||
+ | |||
+ | This section describes the server setting, which must be as same as agent_config.xml with your test target. | ||
+ | |||
+ | *'''Reconnect_Server Section''' | ||
+ | |||
+ | The section for ServerRedCK to test server redundancy. The setting consists of the configuration of a slave server to reconnect. (only support the same server as [Server]) | ||
+ | |||
+ | *'''Device Section''' | ||
+ | |||
+ | The section defines DeviceID. | ||
+ | |||
+ | *'''Topics Section''' | ||
+ | |||
+ | The section describes a topic to subscribe. (only one topic allowed, use '+' to receive messages as many as possible) | ||
+ | |||
+ | *'''HandlerList Section''' | ||
+ | |||
+ | The section describes a list to test handler list. | ||
+ | |||
+ | *'''Capability Section''' | ||
+ | |||
+ | The section describes a list of handlers has to go through capability test. | ||
+ | |||
+ | *'''Report-Upload-Get Section''' | ||
+ | |||
+ | The section describes a list of handlers has to go through report, upload and get test. | ||
+ | |||
+ | *'''Set Section''' | ||
+ | |||
+ | The section describes a list of handlers has to go through set test. | ||
+ | |||
+ | == Modules == | ||
− | + | This section introduces all modules called Checkers in AgentTest used to test functions of an agent. | |
| | ||
− | ''' | + | *'''ConnetionCK''' |
+ | |||
+ | The module is used to check connection functions of an agent such as reconnect function. | ||
+ | |||
+ | *'''GHandlerCapRepCk''' | ||
+ | |||
+ | The module checks general handler’s functions including capability and reported data. | ||
+ | |||
+ | *'''HandlerCapGetSetUploadCK''' | ||
+ | |||
+ | The Checker tests handler’s functions including capability, get, set and upload. | ||
+ | |||
+ | *'''HandlerLSCK''' | ||
+ | |||
+ | The Checker checks handler list to know what handler an agent loads. | ||
+ | |||
+ | *'''ServerRedCK''' | ||
+ | |||
+ | The Checker tests ServerRedundancyHandler’s functions including reconnect function and others. | ||
+ | |||
+ | *'''AServiceCK''' | ||
+ | |||
+ | The Checker checks agent service’s status and functions. | ||
+ | |||
+ | *'''WatchDogCK''' | ||
+ | |||
+ | The Checker checks WatchDog’s status and functions such as restarting a killed agent. | ||
+ | |||
+ | *'''IoTGWCK''' | ||
+ | |||
+ | The Checker checks IoTGWHandler’s functions and the sensor hubs under the gateway. | ||
− | + | *'''AProcessCK''' | |
− | + | The Checker continuously checks agent process’s status. | |
− | |||
− | |||
− | + | All the modules above can be loaded or unloaded according to a user’s requirements or test conditions. By setting a suitable ini configuration, the test result could be simple and easy-to-read, no redundancy report would show. |
Latest revision as of 06:16, 4 October 2016
Introduction
AgentTester – a software tool for testing all sorts of functions and modules of the Agent.
Architecture
The architecture of AgentTester is described as follows. The agent includes three different layers: Main, Module and Library.
- Main Layer
The main executable function to load all the modules required to test functions of an agent.
- Module Layer:
All modules used to test functions of an agent.
- Library Layer:
All libraries required in modules.
Configuration
AgentTester takes an INI file (CheckerSetting.ini) as its configuration to know which modules are required to test an agent according to a user’s requirements. User can modify INI file to load or unload modules for meeting his/her wanted test conditions.
- Modules Section
This section is used to define how many and which modules required to load. And the required operation time for the module.
- Server Section
This section describes the server setting, which must be as same as agent_config.xml with your test target.
- Reconnect_Server Section
The section for ServerRedCK to test server redundancy. The setting consists of the configuration of a slave server to reconnect. (only support the same server as [Server])
- Device Section
The section defines DeviceID.
- Topics Section
The section describes a topic to subscribe. (only one topic allowed, use '+' to receive messages as many as possible)
- HandlerList Section
The section describes a list to test handler list.
- Capability Section
The section describes a list of handlers has to go through capability test.
- Report-Upload-Get Section
The section describes a list of handlers has to go through report, upload and get test.
- Set Section
The section describes a list of handlers has to go through set test.
Modules
This section introduces all modules called Checkers in AgentTest used to test functions of an agent.
- ConnetionCK
The module is used to check connection functions of an agent such as reconnect function.
- GHandlerCapRepCk
The module checks general handler’s functions including capability and reported data.
- HandlerCapGetSetUploadCK
The Checker tests handler’s functions including capability, get, set and upload.
- HandlerLSCK
The Checker checks handler list to know what handler an agent loads.
- ServerRedCK
The Checker tests ServerRedundancyHandler’s functions including reconnect function and others.
- AServiceCK
The Checker checks agent service’s status and functions.
- WatchDogCK
The Checker checks WatchDog’s status and functions such as restarting a killed agent.
- IoTGWCK
The Checker checks IoTGWHandler’s functions and the sensor hubs under the gateway.
- AProcessCK
The Checker continuously checks agent process’s status.
All the modules above can be loaded or unloaded according to a user’s requirements or test conditions. By setting a suitable ini configuration, the test result could be simple and easy-to-read, no redundancy report would show.