We did not find any problems with these test scripts in our tests/code review. It may be related to some special behavior in the server or it requires a specific configuration of the CTT.
Is it possible to share the CTT configuration and the server to reproduce the issue in the Certification lab? If so, please send an email to:
certification@allmendinger.de

In the test script for Session Base/Err-001 the CTT only closed the Secure Channel but left the session open.
In Session Minimum 1/001, the CTT did not close a Secure Channel.

Both test scripts have been updated to close the created session/secure channel.

I noticed, that when (one of the test in) <Address Space Model>/<Address SPace Atomicity> is excuted, a session remains open although the connection is closed. On my machine it is always session UaCttSession_3.
When one of the tests in <Monitored Item Services>/<Monitor Items Deadband Filter> testing the deadbandAbsolute (006 - 009) fail, sessions remain open as well.

Is it possible, that more tests have a simular behaviour?

Please note, that all "DoS attack #2; consume SecureChannels, but CreateSessions in some."-test in the respective Conformance Unit sets (Security Basic 128Rsa15, Security Basic 256Sha256 etc.) fail due to this behaviour.

NOTE that this previous requires a server that is setup to support less than 95 connections.

The original issue was fixed and reviewed - the reopen and additional script have been moved to a cloned issue (related), allowing this set of foxes to be published in this release (cloned issue will wit for next release

reviewed in call, agreed to changes and closed issue