Files
pnoker 372d75b0c9 refactor(core): rename find/query/fetch methods to get per crud law
sweep every module to satisfy the new method-name rule, renaming
about 40 methods together with their interface, implementation, test
and cli call sites: store find() lookups become get(), analytics
queryLatest/queryHistory become getLatest/getHistory, sql helper
query() becomes spec()/sql(), jwks fetch() becomes load(), and the
cursor record component queryDigest becomes requestDigest

no behavior changes; full unit suite (5278 tests) and both quality
gates stay green
2026-09-18 09:53:51 +08:00
..

DC3 E2E

Overview

dc3-e2e is the backend end-to-end test suite of the IoT DC3 platform. It drives a running stack through real HTTP (via REST Assured) and message-queue paths to verify cross-service behavior — command call, event report, point-value storage, RabbitMQ delivery, and TimescaleDB hypertables.

Module Information

  • Group ID: io.github.pnoker
  • Artifact ID: dc3-e2e
  • Packaging: jar (test sources only)

Test Suites

IT Verifies
HarnessSmokeIT The E2E harness itself comes up
RestAssuredHarnessIT REST Assured wiring against the gateway
CommandCallE2eIT Command call end-to-end
EventReportE2eIT Event report end-to-end
RabbitDeliveryIT RabbitMQ message delivery
PostgresHypertableIT TimescaleDB hypertable behavior
MqttVendorNeutralityIT Broker-neutral MQTT delivery across vendors
E2eEnvironmentGuardIT Guards that the target environment is configured

The harness (E2eStack, BaseE2eIT) lives under src/test/java/io/github/pnoker/e2e/harness.

Running

make test-e2e
# = DC3_E2E=true mvn -s .mvn/settings.xml -B -Dmaven.test.skip=false -Dskip.unit.tests=true -pl dc3-e2e -am -Pe2e verify

Requires a Docker-compatible container runtime for the Testcontainers-backed dependencies provided by dc3-common-test.

Dependencies

  • dc3-common-test — Testcontainers and test harnesses
  • dc3-common-model — domain models
  • rest-assured — HTTP assertions