Technology Compatibility Kit (TCK)

The Technology Compatibility Kit(TCK) for all Publisher connectors contains the End-to-end(E2E) tests as well as the SPIs, and the BaseE2ETest that can be extended to inherit useful methods when writing your tests. These tests will ensure that your connector deployment conforms with the connector specification, and is compatible with the expectations of the rest of the Publisher components.

Environment variables

The BaseE2ETest class uses environment variables to configure the deployment URLs that the E2E tests call. Please refer to the javadoc at the top of that file to see the details of these environment variables and how to configure them.

How to use the TCK

In your pom.xml, add:

<dependency>
  <groupId>com.dnastack.dlcon</groupId>
  <artifactId>dlcon-tck</artifactId>
  <version>${dlcon-tck.version}</version>
</dependency>

where the dlcon-tck.version property is the version of the TCK.

<properties>
  <dlcon-tck.version>0.1-XXX</dlcon-tck.version>
</properties>

How to set up

Create META-INF/sercices in src/{main,test}/java/resources.

Create com.dnastack.dlcon.tck.spi.BackendApiClientFactory where each line is a fully-qualified class name to a backend API client factory.

How to run with IntelliJ

In your Run/Debug configuration for JUnit:

Select “Modify options” in Build and run. From the context menu, select “Search all tests” and then “Across module dependencies”.