Latest test reports are available:

• Specifications
• Raft
• Istanbul

Prerequisites

• Java 8
• Maven 3.5.x
• Solidity Compiler (make sure solc is installed and not solcjs)
  • For MacOS: use brew
  • For Linux: use apt, snap or emerge
  • For Windows: download from here
• Gauge

Writing Tests

• Using Gauge test automation framework
• Test Specs are stored in src/specs folder
  • Folder 01_basic contains specifications which describe Quorum's basic functionalities. All specifications must be tagged as basic
  • Folder 02_advanced contains specifications which are for making sure Quorum's basic functionalities are working under different conditions in the chain. All specifications must be tagged as advanced
• Glue codes are written in Java under src/test/java folder

Running Tests

• When quorum-cloud is used to provision Quorum Network:
  • Start SOCKS proxy for SSH tunneling. E.g.: listening on port 5000

    $ ssh -D 5000 -N -o ServerAliveInterval=30 -i <private_key> ec2-user@<bastion node>
    

  • Obtain the nodes metadata from Bastion Node (/qdata/quorum_metadata) and create a file config/application-local.yml with content similar to a sample file in config folder.
• When using quorum-examples, rename config/application-local.7nodes.yml to config/application-local.yml
• Run mvn clean test
  • By default in Travis, specifications/scenarios with tags basic and advanced (including targeted consensus, e.g.: basic-raft, raft or basic-istanbul, istanbul) are run
  • By defautl in local machine, only specifications/scenarios with tags basic are run. Refer to Gauge documentation and Gauge Maven Plugin to see how to run specs selectively. E.g.: mvn test -Dtags="advanced && istanbul" to run only advanced specifications and scenarios tagged with istanbul

Logging

• Set environment variable: LOGGING_LEVEL_COM_QUORUM_GAUGE=DEBUG

---