Skip to content

Latest commit

 

History

History
60 lines (36 loc) · 2.43 KB

README.md

File metadata and controls

60 lines (36 loc) · 2.43 KB
Raw

nem2-e2e-tests

Integration and e2e tests for the catapult project.

Prerequisites

Installation

  1. Clone this repository:
git clone --recursive https://github.com/nemtech/nem2-e2e-tests.git

  1. Install the Cucumber-JVM. You can install the Cucumber plugin for IntelliJ if you want to run the test from the IDE.

  2. Get the latest catapult-service-bootstrap and start the service.

  3. Update the following properties under the integrationtests/src/test/resources/configs/config-default.properties file to match your bootstrap environment.

    • apiServerPublicKey: Public key of the API server. You can find it in build/catapult-config/api-node-0/userconfig/resources/peers-api.json.
    • userPrivateKey: Private key of the user which will be use to sign each transaction. You can find a list of users in build/generated-addresses/addresses.yaml file under the nemesis_addresses section.
    • mosaicId: Network currency mosaic identifier. You can find the network mosaic id going to http://localhost:3000/#/account/<public_key_of_the_user>

Running the tests

  1. Open the folder where you have cloned this repository.
  2. Move to the integrationtests folder.
cd integrationtests
  1. Build and runt the tests.
mvn test

Note: If you have installed an IDE, you cnan run the tests and debug them from there.

Contributing

Before contributing please read this.

Adding new tests

The file structure of the automation tests is as follows:

  • Feature files: integrationtests/src/test/resources/io/nem.
  • Cucumber steps files: integrationtests/src/test/java/io/nem/automation.

In each of these folders, there is an example folder which has a feature and cucumber steps file respectively.

Before adding tests, check the nem2-scenarios repository for a list of Cucumber feature files already defined. This repository gathers the set of scenarios that should be automated.

To check if a feature file from the nem2 scenarios is already automated, check if the feature file is present in this repository.