added a generated file
store and check the path to the UaServerCPP demo server
copy the demoserver.py file to the unittests/pyuaf directory
added python software to command the demo server
the new unittests (compatible with UaServerCPP of the SDKv1.4 instead of UaDemoServer of the SDKv1.3) will be put in this directory
demoserver can't easily be started/stopped in Windows, so we remove our DemoServerRunner software, and require the demo server to be run manually
If no starting points of relative paths can be resolved, previously an unexpected error was raised.
However this should only result in a ReadResult/WriteResult/... with a bad overallStatus. It should
not immidiately result in a bad "client-side" error (corresponding to an exception in PyUAF), because
the problem may well be on the server side.
the test scripts will remain in a 'pyuaftests' folder instead of a 'pyuaf' folder, to avoid name conflicts
unittests helper functionality is now available in pyuaf.util.unittesting
bugfix: when a subscription is now deleted (e.g. via Client::manuallyUnsubscribe), its status is now changed to DELETED. Also some logging has been added
bugfix: a Bad status is now returned as default case
run all_tests.py to run all unit tests from now on
all helper functionality for the unit testing is now part of this module
Migrated from UaDemoServer (SDK v1.3 or lower) to UaServerCPP (SDK v1.4 or higher), and also changed the code so that Python's standard 'unittest' module is now used
new scripts to run the unit tests
copy the new unittesting.py module to the lib/util directory
bugfix in the example: some missing imports
migrated from UaDemoServer (SDK version 1.3 or lower) to UaServerCPP (SDK version 1.4 or higher)
add an example for the new additional constructor
changed OpcUaId_ExclusiveDeviationAlarmType_Acknowledge to OpcUaId_ExclusiveDeviationAlarmType since the former is not available anymore in the SDK v1.4