Releases: Draegerwerk/SDCcc
v10.0.0
Changelog
All notable changes to SDCcc will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
[10.0.0] - 2025-05-22
Added
- support for Kotlin
- storing of IP addresses of inbound messages in the database
- a command line parameter to not create subdirectories in the test run directory
- a command line parameter to print the version of the sdccc test tool
- add config parameter to set the minimum amount of time the test tool is supposed to collect data
- unmarshal SOAP messages with casting to a configurable class
Changed
- the license to a non-commercial license, see LICENSE
- the SoapMarshalling is now configurable regarding packages to scan for JAXB classes and the schemas for validation
- the collected data is now flushed after each precondition
- moved test case specific parameter into separate file test_parameter.toml
- sdc-ri version to 6.2.2
- build is now using gradle instead of maven
- value of GLUE.R0036_0 from true to false in the example config test_configuration.toml
- t2iapi version to 4.2.0
Fixed
- support multiple mds for test case for BICEPS.R5042
- inconsistent messaging in SDCcc logs ("No problems were found" and "Test run was invalid" one after another.)
- incorrect behavior of the configuration option SDCcc.SummarizeMessageEncodingErrors
- test for BICEPS.R5003 does not check MdDescriptionVersion and MdStateVersion anymore (see PR 232)
Removed
- consumer test related implementations
internal-baseline-001
Changelog
All notable changes to SDCcc will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
[Unreleased]
Added
- support for Kotlin
- storing of IP addresses of inbound messages in the database
- a command line parameter to not create subdirectories in the test run directory
- a command line parameter to print the version of the sdccc test tool
- add config parameter to set the minimum amount of time the test tool is supposed to collect data
- unmarshal SOAP messages with casting to a configurable class
Changed
- the SoapMarshalling is now configurable regarding packages to scan for JAXB classes and the schemas for validation
- the collected data is now flushed after each precondition
- moved test case specific parameter into separate file test_parameter.toml
- sdc-ri version to 6.2.0
- build is now using gradle instead of maven
- value of GLUE.R0036_0 from true to false in the example config test_configuration.toml
- t2iapi version to 4.2.0
Fixed
- support multiple mds for test case for BICEPS.R5042
- inconsistent messaging in SDCcc logs ("No problems were found" and "Test run was invalid" one after another.)
- incorrect behavior of the configuration option SDCcc.SummarizeMessageEncodingErrors
- test for BICEPS.R5003 does not check MdDescriptionVersion and MdStateVersion anymore (see PR 232)
Removed
- consumer test related implementations
v9.0.2
Changelog
All notable changes to SDCcc will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
[9.0.2] - 2025-01-27
Fixed
- SequenceIds are now ordered by the timestamp of the first message that used them
v9.0.1
Changelog
All notable changes to SDCcc will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
[9.0.1]
Fixed
- biceps:C-11, biceps:C-12, biceps:C-13, biceps:C-14 and biceps:C-15 no longer fails incorrectly if a DescriptionModificationReport with the same MdibVersion has been sent for the respective EpisodicReport.
v9.0.0
[9.0.0] - 2024-02-23
Added
- a command line parameter to change the log level threshold of the log file
- a parameter in a config file to specify the ciphers being used in the TLS protocol
Changed
- t2iapi version to 4.1.0
Fixed
- a performance issue with xml unmarshalling due to finding an interface implementation for TransformerFactory
- slowdown and high memory usage due to large unfiltered logs, filter can be configured, default shrinks the log
- autocommit of the database being on, it is now always off
- local address resolver sometimes giving a wrong address
- local address resolver doing a probe which may not be tolerated by some peers
- potential NullPointerException in DescriptionModificationUptPrecondition
- the test case for Glue:R0036_0 not accepting a SOAPFault as a valid answer for Subscribe messages
- ReportWriter.write() could be called with ReportTypes it did not support.
- the SDCcc.TLS.EnabledProtocols parameter being ignored for the internal TLS configuration
9.0.0-rc1
[9.0.0-rc1 / 9.0.0-SNAPSHOT.77a738a] - 2024-02-23
Added
- a command line parameter to change the log level threshold of the log file
- a parameter in a config file to specify the ciphers being used in the TLS protocol
Changed
- t2iapi version to 4.1.0
Fixed
- a performance issue with xml unmarshalling due to finding an interface implementation for TransformerFactory
- slowdown and high memory usage due to large unfiltered logs, filter can be configured, default shrinks the log
- autocommit of the database being on, it is now always off
- local address resolver sometimes giving a wrong address
- local address resolver doing a probe which may not be tolerated by some peers
- potential NullPointerException in DescriptionModificationUptPrecondition
- the test case for Glue:R0036_0 not accepting a SOAPFault as a valid answer for Subscribe messages
- ReportWriter.write() could be called with ReportTypes it did not support.
- the SDCcc.TLS.EnabledProtocols parameter being ignored for the internal TLS configuration
v8.0.1
Changelog
All notable changes to SDCcc will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
[8.0.1] - 2023-09-13
Fixed
- test failures are treated as errors
v8.0.0
Changelog
All notable changes to SDCcc will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
[8.0.0] - 2023-09-12
Added
- location query based discovery
- requirement test execution logging
- test for glue:R0056
- configuration option to change the maximum waiting time during connection establishment
- SDCcc version is written to the log and into the result XML files.
- message encoding errors are summarized by default, but all information is available via the configuration option
SDCcc.SummarizeMessageEncodingErrors. - checking for message encoding errors can be disabled using the configuration option SDCcc.EnableMessageEncodingCheck.
- when enabled, SDCcc also checks if message bodies can be decoded using the encoding specified.
- configuration option SDCcc.Network.MulticastTTL to configure the Time To Live of the Multicast Packets used for Discovery.
- precondition for biceps:R5024 to trigger description modification reports for test data
Changed
- the precondition of biceps:R0133 so that it is now easier to satisfy.
- the precondition of biceps:R0034_0 so that it is now easier to satisfy.
- the precondition of biceps:C5 and biceps:R5052 so that it can be satisfied by devices that do not support updating
MDS descriptors. - SDCri version 5.0.0
- t2iapi version 3.0.0
Fixed
- the occurrence of the sequence ']]>' in the content of CDATA sections in the result xmls
- setComponentActivation stores incorrect manipulation data in the database resulting in no test data being available for 5-4-7_* tests
- that preconditions of the following requirements could not handle the T2IAPI manipulation result RESULT_NOT_SUPPORTED: biceps:R0029_0 biceps:R0116 biceps:5-4-7_0_0 biceps:5-4-7_1 biceps:5-4-7_2 biceps:5-4-7_3 biceps:5-4-7_4 biceps:5-4-7_5 biceps:5-4-7_6_0 biceps:5-4-7_7 biceps:5-4-7_8 biceps:5-4-7_9 biceps:5-4-7_10 biceps:5-4-7_11 biceps:5-4-7_12_0 biceps:5-4-7_13 biceps:5-4-7_14 biceps:5-4-7_15 biceps:5-4-7_16 biceps:5-4-7_17
- biceps:R0034_0 does not track changes when reinserting descriptors.
- report duplication issue in biceps:C11-C15, biceps:C5, biceps:R5046_0, biceps:B-284_0 as well as biceps:R5003.
- biceps:5-4-7 tests confusing changes made by SetComponentActivation manipulations with changes made by SetMetricStatus.
- glue:R0036_0 test can be blocked by long-running t2iapi RPCs.
- biceps:5025_0 test case could not be satisfied by devices that do not support inserting and removing descriptors.
- SDCcc previously terminated with exitCode 0 despite certain Errors.
8.0.0-SNAPSHOT-2023-09-04
Changelog
All notable changes to SDCcc will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
[Unreleased]
Added
- location query based discovery
- requirement test execution logging
- test for glue:R0056
- configuration option to change the maximum waiting time during connection establishment
- SDCcc version is written to the log and into the result XML files.
- message encoding errors are summarized by default, but all information is available via the configuration option
SDCcc.SummarizeMessageEncodingErrors. - checking for message encoding errors can be disabled using the configuration option SDCcc.EnableMessageEncodingCheck.
- when enabled, SDCcc also checks if message bodies can be decoded using the encoding specified.
- configuration option SDCcc.Network.MulticastTTL to configure the Time To Live of the Multicast Packets used for Discovery.
- precondition for biceps:R5024 to trigger description modification reports for test data
Changed
- SDCri version 5.0.0-SNAPSHOT
- the precondition of biceps:R0133 so that it is now easier to satisfy.
- the precondition of biceps:R0034_0 so that it is now easier to satisfy.
- the precondition of biceps:C5 and biceps:R5052 so that it can be satisfied by devices that do not support updating
MDS descriptors.
Fixed
- the occurrence of the sequence ']]>' in the content of CDATA sections in the result xmls
- setComponentActivation stores incorrect manipulation data in the database resulting in no test data being available for 5-4-7_* tests
- that preconditions of the following requirements could not handle the T2IAPI manipulation result RESULT_NOT_SUPPORTED: biceps:R0029_0 biceps:R0116 biceps:5-4-7_0_0 biceps:5-4-7_1 biceps:5-4-7_2 biceps:5-4-7_3 biceps:5-4-7_4 biceps:5-4-7_5 biceps:5-4-7_6_0 biceps:5-4-7_7 biceps:5-4-7_8 biceps:5-4-7_9 biceps:5-4-7_10 biceps:5-4-7_11 biceps:5-4-7_12_0 biceps:5-4-7_13 biceps:5-4-7_14 biceps:5-4-7_15 biceps:5-4-7_16 biceps:5-4-7_17
- biceps:R0034_0 does not track changes when reinserting descriptors.
- report duplication issue in biceps:C11-C15, biceps:C5, biceps:R5046_0, biceps:B-284_0 as well as biceps:R5003.
- biceps:5-4-7 tests confusing changes made by SetComponentActivation manipulations with changes made by SetMetricStatus.
8.0.0-SNAPSHOT-2023-09-01
Changelog
All notable changes to SDCcc will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
[Unreleased]
Added
- location query based discovery
- requirement test execution logging
- test for glue:R0056
- configuration option to change the maximum waiting time during connection establishment
- SDCcc version is written to the log and into the result XML files.
- message encoding errors are summarized by default, but all information is available via the configuration option
SDCcc.SummarizeMessageEncodingErrors. - checking for message encoding errors can be disabled using the configuration option SDCcc.EnableMessageEncodingCheck.
- when enabled, SDCcc also checks if message bodies can be decoded using the encoding specified.
- configuration option SDCcc.Network.MulticastTTL to configure the Time To Live of the Multicast Packets used for Discovery.
- precondition for biceps:R5024 to trigger description modification reports for test data
Changed
- SDCri version 5.0.0-SNAPSHOT
- the precondition of biceps:R0133 so that it is now easier to satisfy.
- the precondition of biceps:R0034_0 so that it is now easier to satisfy.
- the precondition of biceps:C5 and biceps:R5052 so that it can be satisfied by devices that do not support updating
MDS descriptors.
Fixed
- the occurrence of the sequence ']]>' in the content of CDATA sections in the result xmls
- setComponentActivation stores incorrect manipulation data in the database resulting in no test data being available for 5-4-7_* tests
- that preconditions of the following requirements could not handle the T2IAPI manipulation result RESULT_NOT_SUPPORTED: biceps:R0029_0 biceps:R0116 biceps:5-4-7_0_0 biceps:5-4-7_1 biceps:5-4-7_2 biceps:5-4-7_3 biceps:5-4-7_4 biceps:5-4-7_5 biceps:5-4-7_6_0 biceps:5-4-7_7 biceps:5-4-7_8 biceps:5-4-7_9 biceps:5-4-7_10 biceps:5-4-7_11 biceps:5-4-7_12_0 biceps:5-4-7_13 biceps:5-4-7_14 biceps:5-4-7_15 biceps:5-4-7_16 biceps:5-4-7_17
- biceps:R0034_0 does not track changes when reinserting descriptors.
- report duplication issue in biceps:C11-C15, biceps:C5, biceps:R5046_0, biceps:B-284_0 as well as biceps:R5003.