Skip to content
TesseraQL

Build

Terminal window
mvn -B -ntp verify

TesseraQL 1.x build policy:

  • baseline: Java 21
  • compatibility: Java 25
  • Maven multi-module
  • Maven plugin first
  • Gradle plugin later

Formatting

Section titled “Formatting”

Java formatting is enforced in the build: spotless:check runs during verify against the shared profile config/eclipse-formatter.xml (4-space indent, 100 columns; hand-wrapped lines and comments are left as authored). Imports are normalized too: static imports first, then one alphabetical block, unused imports removed. VS Code applies the same profile and import rules on save (java.format.settings.url, java.completion.importOrder, organize-imports on save - preconfigured in the Dev Container). To fix violations:

Terminal window
./mvnw spotless:apply

Compiler warnings

Section titled “Compiler warnings”

javac warnings fail the build (-Xlint:all with failOnWarning; the -processing, -serial, -this-escape, and -classfile categories are excluded as noise). Suppress a deliberate violation locally with @SuppressWarnings and a comment explaining why - for example, a codec that must not close a caller-owned stream, or a Testcontainers field whose lifecycle the @Container extension manages.

Test reports and coverage

Section titled “Test reports and coverage”

The tesseraql:test and tesseraql:coverage goals run the app’s declarative suites and write reports under target/tesseraql-reports/:

  • junit/TEST-tesseraql.xml, tesseraql-result.json, index.html — test results (JUnit XML / JSON / HTML)
  • allure-results/*-result.json — Allure 2 result files (allure generate ready)
  • coverage/sql-coverage.json — SQL line/branch coverage plus the item-coverage kinds
  • coverage/cobertura.xml, coverage/sonarqube.xml — Cobertura and SonarQube generic coverage exports for CI publishers
  • coverage/coverage.sarif — coverage gaps as SARIF for code scanning

Coverage kinds beyond SQL line/branch (design ch. 14): assertion (cases that assert), iam-contract (standard identity contracts exercised), route / security (manifest routes — and the subset declaring security: — whose SQL artifacts the suites exercise), saml (the identity contracts the SAML user-link login path executes, when linking is enabled), scim (the contract SQL files wired via tesseraql.scim.*), validation (every validate: rule, covered by the validate cases that evaluate it), notification (every notify: declaration of routes and jobs, covered by the notify cases that evaluate it), document (every printable-document export, covered like routes), and message (every messages/<locale>.yml catalog, covered by the messages cases that read it). Kinds with nothing declared report 1.0.

The coverage goal gates on coverage.thresholds.* percentages from the app config (or the -Dtesseraql.sqlLineThreshold / -Dtesseraql.sqlBranchThreshold defaults):

coverage:
  thresholds:
    sqlLine: 80
    sqlBranch: 80
    route: 90        # any kind name gates that kind; absent kinds are not gated
    security: 100

Dialect integration tests

Section titled “Dialect integration tests”

PostgreSQL and MySQL integration tests run on every ./mvnw verify. The Oracle and SQL Server plan-guard tests use large container images and are opt-in:

Terminal window
# Query Plan Guard against real Oracle / SQL Server
./mvnw -pl tesseraql-coverage-core test -Dtesseraql.dialect.its=true \
  -Dtest='OraclePlanGuardIntegrationTest,SqlServerPlanGuardIntegrationTest'


# Full runtime portability (framework migrations, stores, identity pack, a served route)
./mvnw -pl tesseraql-camel-runtime test -Dtesseraql.dialect.its=true \
  -Dtest='OraclePortabilityIntegrationTest,SqlServerPortabilityIntegrationTest'