Moler - library to help in building automated tests¶
Moler key features
- Event observers & callbacks (alarms are events example)
- to allow for online reaction (not offline postprocessing)
- Commands as self-reliant object
- to allow for command triggering and parsing encapsulated in single object (lower maintenance cost)
- Run observers/commands in the background
- to allow for test logic decomposition into multiple commands running in parallel
- to allow for handling unexpected system behavior (reboots, alarms)
- State machines -> automatic auto-connecting after dropped connection
- to increase framework auto-recovery and help in troubleshooting “what went wrong”
- Automatic logging of all connections towards devices used by tests
- to decrease investigation time by having logs focused on different parts of system under test
- Installation
- moler
- moler.config package
- moler.device package
- Submodules
- moler.device.abstract_device module
- moler.device.adbremote module
- moler.device.adbremote2 module
- moler.device.atremote module
- moler.device.device module
- moler.device.juniper_ex module
- moler.device.junipergeneric module
- moler.device.pdu_aten module
- moler.device.proxy_pc module
- moler.device.proxy_pc2 module
- moler.device.scpi module
- moler.device.state_machine module
- moler.device.textualdevice module
- moler.device.unixlocal module
- moler.device.unixremote module
- moler.device.unixremote2 module
- Module contents
- moler.events package
- moler.parser package
- moler.util package
- Submodules
- moler.util.cmds_events_doc module
- moler.util.connection_observer module
- moler.util.connection_observer_life_status module
- moler.util.converterhelper module
- moler.util.devices_SM module
- moler.util.loghelper module
- moler.util.moler_serial_proxy module
- moler.util.moler_test module
- Module contents
- Code Examples