Skip to main content
This page explains how to test and validate a new or existing connector to ensure it functions correctly before deployment.

​
Testing overview

Unit tests

Test individual components and routes in isolation

Integration tests

Test connector interactions with external services

Contract tests

Validate API contracts and OpenAPI specifications

End-to-end tests

Test complete flows from request to response

​
Run unit tests

Unit tests are supported within connectors through the camel-test-junit5 library. This test library is available for every connector from the grandcentral-bom.

​
Running tests with maven

Execute unit tests using Maven: 
mvn test

​
Running specific tests

Run a specific test class: 
mvn test -Dtest=GenericApiConnectorTest
Run specific test methods: 
mvn test -Dtest=GenericApiConnectorTest#testSuccessfulRequest

​
Unit test examples

For comprehensive unit test examples, see the Grand Central connector template repository.

​
Example: Basic route test

@QuarkusTest
public class GenericApiConnectorTest {

    @Test
    public void testSuccessfulRequest() {
        given()
            .contentType(ContentType.JSON)
            .body("{\"name\": \"test\"}")
        .when()
            .post("/api/connector/process")
        .then()
            .statusCode(200)
            .body("status", equalTo("success"));
    }
}

​
Example: Mock external service

@QuarkusTest
public class ExternalServiceTest {

    @InjectMock
    ExternalServiceClient externalService;

    @Test
    public void testWithMockedService() {
        // Mock external service response
        when(externalService.getData())
            .thenReturn(new ResponseData("mocked"));

        given()
            .get("/api/data")
        .when()
        .then()
            .statusCode(200)
            .body("data", equalTo("mocked"));
    }
}

​
Test configuration

​
Test properties

Configure test-specific properties in src/test/resources/application.properties: 
# Test profile
quarkus.test.profile=test

# Mock external endpoints
connector.baseUrl=http://localhost:8081
connector.mock.enabled=true

# Logging for tests
quarkus.log.level=DEBUG
quarkus.log.category."com.backbase.gc".level=DEBUG

​
Test profiles

Create custom test profiles for different scenarios: 
@TestProfile(CustomTestProfile.class)
public class CustomConnectorTest {
    // Test implementation
}

public class CustomTestProfile implements QuarkusTestProfile {
    @Override
    public Map<String, String> getConfigOverrides() {
        return Map.of(
            "connector.baseUrl", "http://test-server:8080",
            "connector.timeout", "5000"
        );
    }
}

​
Integration testing

​
Wiremock for external services

Use WireMock to mock external HTTP services: 
@QuarkusTest
@QuarkusTestResource(WireMockExtensions.class)
public class IntegrationTest {

    @InjectWireMock
    WireMockServer wireMock;

    @Test
    public void testExternalApiCall() {
        // Stub external API
        wireMock.stubFor(
            get(urlEqualTo("/external/api"))
                .willReturn(aResponse()
                    .withStatus(200)
                    .withBody("{\"result\": \"success\"}")
                )
        );

        // Test connector call
        given()
            .get("/api/process")
        .then()
            .statusCode(200);
    }
}

​
API contract validation

​
OpenAPI specification validation

Validate that your connector implementation matches the OpenAPI specification: 
@Test
public void validateOpenAPIContract() {
    given()
        .get("/q/openapi")
    .then()
        .statusCode(200)
        .body(matchesJsonSchemaInClasspath("openapi-schema.json"));
}

​
Test coverage

​
Generate coverage reports

Generate test coverage reports with JaCoCo: 
mvn clean verify
View the coverage report at target/site/jacoco/index.html.

​
Coverage goals

Aim for the following coverage targets:
  • Line Coverage: Minimum 80%
  • Branch Coverage: Minimum 75%
  • Method Coverage: Minimum 85%

​
Performance testing

​
Load testing with Gatling

Run performance tests to validate connector behavior under load: 
class ConnectorLoadTest extends Simulation {
  val httpProtocol = http
    .baseUrl("http://localhost:8080")

  val scn = scenario("Basic Load Test")
    .exec(http("process_request")
      .post("/api/connector/process")
      .body(StringBody("""{"data": "test"}"""))
      .check(status.is(200)))

  setUp(
    scn.inject(
      rampUsers(100) during (60 seconds)
    )
  ).protocols(httpProtocol)
}

​
Continuous testing

​
Running tests in CI/CD

Include tests in your CI/CD pipeline: 
# Example github actions workflow
name: Test
on: [push, pull_request]

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-java@v3
        with:
          java-version: '17'
      - name: Run tests
        run: mvn clean verify
      - name: Upload coverage
        uses: codecov/codecov-action@v3

​
Validation checklist

Before deploying your connector, ensure:
  • All unit tests pass
  • Coverage meets minimum thresholds
  • Edge cases are covered
  • External service interactions are tested
  • Error scenarios are validated
  • Timeouts and retries work correctly
  • OpenAPI specification is valid
  • Request/response schemas match
  • All endpoints are documented
  • Load tests pass successfully
  • Response times are acceptable
  • Resource usage is within limits

​
Troubleshooting tests

​
Common issues

Check for environment-specific configurations or dependencies
  • Add proper wait conditions
  • Avoid time-based assertions
  • Use deterministic test data
  • Parallelize test execution
  • Use test profiles to skip heavy tests during development
  • Optimize test setup and teardown

​
Next steps

After successfully testing your connector: