Java Connector
  • Java Connector
  • Concepts
    • Feature Summary
    • Terminology
    • Account Model
    • Packet Switching Fabric
    • Exchange Rates
    • Routing Table Design
    • Destination Address Handling
    • Balance Tracking
    • Settlement
  • Connector Configuration
  • Connector Configuration Properties
  • Persistence Initialization
  • Local STREAM Packet Termination
  • Connector Operation
  • Running with Docker
  • Peering: ILP-over-HTTP
  • Settlement: XRP Ledger
  • Running on GCP
  • Security Guide
    • Connector Crypto
    • test-jwt.io
    • Generating Keys
    • Spring Boot with TLS
  • API References
    • Admin API
  • Tutorials
    • ILP TestNet: Getting Started
  • Contributing
    • Connector Development
    • Project Testing
  • Releases
    • Changelog
Powered by GitBook
On this page
  • Unit Tests
  • Integration Tests
  • Project Build Switches
  • Run Default IT Suite
  • Skip Unit Tests
  • Skip Integration Tests
  • Skip All Tests
  • Run Settlement ITs
  • Run Performance ITs

Was this helpful?

  1. Contributing

Project Testing

PreviousConnector DevelopmentNextChangelog

Last updated 5 years ago

Was this helpful?

This project includes various tests to ensure the correctness of the product.

Test are segmented into two broad categories, Unit Tests and Integration Tests. By default all unit tests are enabled, and most Integration tests are also enabled, although certain classes of integration tests only run inside of the .

Unit Tests

Each class in this implementation should have high levels of unit test coverage. Execution of these tests is orchestrated by the , and can be enabled or disabled via command line-switches as detailed below. By default,

Integration Tests

This project includes a single module housing all integration tests: . By default, most integration tests execute in the local build environment, whereas all Integration tests execute in the CI environment.

There are various types of Integration test:

  • Performance ITs: Validate the performance characteristics of the product.

  • IlpOverHttp ITs: Validate functionality of two or more nodes peering with each other using .

  • Settlement ITs: Validate functionality of the Settlement subsystems using multiple nodes.

Project Build Switches

The following commands can be used to build the project while skipping various test suites.

Run Default IT Suite

mvn verify

Skip Unit Tests

mvn verify -DskipUTs

Skip Integration Tests

mvn verify -DskipITs

Skip All Tests

mvn verify -DskipTests

Run Settlement ITs

mvn verify -Psettlement

Run Performance ITs

mvn verify -Pperformance
CI environment
Maven Surefire Plugin
ilpv4-connector-it
ILP-over-Http