Impulse Dev Manual
HomePricingContact Us
  • Understanding Impulse Sync
  • Understanding how Impulse diffs content
  • Understanding Job Scheduling
  • Motation
    • Content Motation
    • Definition Motation
    • Domain Motation
    • Folder Motation
    • Language Motation
    • Relationship Motation
    • Tag Motation
  • Connectors
    • Source Connector
    • Destination Connector
    • Go Code
    • IDs
    • ID Mapping
    • Testing Controller
      • Implementation
  • Motators Binary
    • Implementation
    • Go Code
  • Services
    • Connector Depot
    • Motator Binary Depot
    • Job Depot
    • Endpoint Depot
    • Sync Manager
    • Content Diffuser
    • Pickup Taxi
    • Dropoff Taxi
    • Pipeliner
    • Scheduler
    • Motator
    • Motator Service
  • Watchdog Process
    • Watchdog flow
  • Impulse License
  • Troubleshooting
    • Job Config
    • Transaction Audit Trail
  • gRPC
    • Protocol buffer compiler
  • Test Commands
  • Glossary
Powered by GitBook
On this page
  • Basics
  • Steps

Was this helpful?

  1. Connectors
  2. Testing Controller

Implementation

PreviousTesting ControllerNextMotators Binary

Last updated 2 years ago

Was this helpful?

Basics

  • Remember a connector could be a source or destination one. Each will need a set of configuration files (explained below) exported to astro

Steps

  • In your connector implement this interface:

  • Create a binary and place it under the proper folder under impulse, for example:

CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -mod=mod -a -installsuffix cgo -o ../impulse/docker-tools/compose-template/connector-test/dotcms/destination/testRunnerDestination ./cmd/test-runner-destination
  • Provide the configuration files under astro. For example for dotCMS + source () the path would look like this: impulse/docker-tools/compose-template/connector-test/dotcms/source

    • astro-config-extension.conf: Property file for your testing binary.

    • config.json: Contains specific properties for each of the ks-min and ks-max types of testing.

    • content-mapping.json (optional): Content Mapper configuration, in order to work, the sync needs to have this file in both source and destination.

    • docker-compose.yml: Docker config for the tested system including the transformer and adapter.

    • ks-max.sh: curl commands to config system endpoints, taxis aand adapters for type ks-max

    • ks-min.sh: curl commands to config system endpoints, taxis aand adapters for type ks-min

https://github.com/motiv-labs/go-test-runner-destination/blob/main/destination-connector-tester.go
Github Link