What is Tester?
Key Features
- Automated testing of DDS-based systems
- Dynamic discovery of DDS entities
- Domain-Specific scripting Language (DSL) for test scenario’s
- Batch execution of regression tests
- Debugging of distributed DDS system
- One-click definition of a monitoring-time-line
- Analysis/comparison of topics / instances and samples
- Virtual topic-attributes to dramatically ease analysis
- System-browser of DDS entities (app’s / readers / writers)
- Connectivity and QoS-conflict monitoring / detection
- Statistics-monitoring of applications and services
- Integrated IDE
- Syntax highlighting editor, script-executor and Sample Logger
- One-click relations between script, logs and timeline
- Optional integration of message-interfaces with DDS interactions
The Vortex OpenSplice Tester Tool has the following characteristics:
- 100% Java based
- Remote-connection to target system (option)
- Integrated charting capability
- DDS-specific DSL alongside javascript, python or ruby
The Vortex OpenSplice Tester Tool is complementary to the Vortex OpenSplice Tuner Tool, in that the Tuner facilitates ‘white-box’ application monitoring and tuning (you can look ‘inside’ an application and monitor its behaviour and / or even change its Qualities of Service (QoS) parameters ‘on-the-fly’). Whereas the Vortex OpenSplice Tester Tool provides ‘black-box’ system testing and debugging of DDS-based systems (it ‘stimulates’ a DDS-system by injection of information and can react-on / validate / display / chart the system’s responses).
Is it possible to change the rate at which OpenSplice Tester runs from the default 10 Hz?
When starting the tester I get the error “System clock has been set back (-40)”
“License checkout failed! Caught com.reprisesoftware.rlm.RlmException: System clock has been set back (-40)”
OpenSplice tester uses RLM for its licensing. RLM detects windback by looking for future-dated files (access and modified times) in system directories. In many cases just running the system for a little while with the correct date will access the future-dated files and the problem will clear itself. Often a reboot helps too. If it doesn’t clear itself you will have to go into those directories and look for the offending file and set them to the current time by accessing them. On windows, RLM looks in windows or winnt. On linux, RLM looks in /etc, /var/adm, and /var/log.