See show_tag
Implement a brand new interface using two threads, one for the transmission and one for the reception.
Currently adapted modules: - Proxy Auxiliary - CCProxy channel - Communication Auxiliary - DUT Auxiliary - Record Auxiliary - Acroname Auxiliary - Instrument Auxiliary - UDS Auxiliary - UDS server Auxiliary
There is not API changes, therefor, as user, your tests should not be affected.
Incompatibilities with the agnostic proxy are now resolved. You should be able to use it again.
Add a context manager, tester present sender, that send cyclic tester present frames to keep UDS session alive more than 5 seconds
See uds_auxiliary
RTT connector now creates a log folder if it does not exist instead of throwing an error.
To save on memory, the communication auxiliary does not collect received messages automatically anymore. The functionality is now available with the context manager collect_messages
.
See examples/templates/suite_com/test_com.py
The collected messages by the Communication auxiliary can still be cleared with the API method :py:meth`~pykiso.lib.auxiliaries.communication_auxiliary.CommunicationAuxiliary.clear_buffer`
See communication_auxiliary
refactor/redesign of the device under test auxiliary to fit with the brand new double threaded auxiliary interface
adapt the record auxiliary to fit with the brand new double threaded auxiliary interface
adapt the acroname auxiliary to fit with the brand new double threaded auxiliary interface
Instead of having only the 2 tags "variant" and "branch_level" to select tests, users can now set any tagname.
See: define_test_information
for more details.
To avoid extra waiting time during long/heavy UDS data exchange(flashing) expose the parameter tpWaitTime from kiso-testing-python-uds for uds auxilary send_uds_raw method
See uds_auxiliary
Lightweight UDS auxiliary configuration ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The add of an .ini file to configured the UDS auxiliary and it variant (server) is no more mandatory, every parameter is now reachable in the .yaml file.
See examples/uds.yaml
In addition, if the tp_layer and uds_layer parameters are not given at yaml level a default configuration is applied.
See uds_auxiliary
To let users decide the level of information they want to see in their logs, new log levels have been defined. When launched normally only the logs in the tests and the errors will be active. The option -v (--verbose) should be used to display the internal logs of the framework.
See run_the_tests