Enabling the support for the acceptance tests to the generated DenoJS driver is a step towards to release it as library.

During the acceptance tests run, the browser-channel presents some errors handling write request when the socket was already closed. Verifying the socket status does not prevent the error, since the sockets which appears as connected could also presents the error because of a non-updated status (or the status get changed while the message is being send). This error is no catchable and make the application get closed.

DenoChannel was introduced for fixing this issue. This implementation uses the Deno.Conn and Deno.TlsConn for socket communication which causes a few drawbacks such as:

• TRUST_ALL_CERTIFICATES should be handle by --unsafely-ignore-certificate-errors and not by driver configuration. See, https://deno.com/blog/v1.13#disable-tls-verification;
• The Deno.TlsConn fails hard in certificate error which causes the application closes;

Testkit Backend

The Deno Testkit Backend implementation re-uses most of the NodeJS implementation. Adjustments in the file import and the removal of a direct neo4j dependency¹ in the common code was need for making it possible.

Socket connection with testkit, backend controller and new entry-point were re-implemented for Deno backend. This implementation is located at /packages/testkit-backend/deno and documented at /packages/testkit-backend/deno/README.md

¹ Other NodeJs/NPM dependencies like tls were also moved for Node specific files.