Integration tests are part of Software Developer Kit repository and dont need integration repository

[theblockstalk]

Definition of done:

• [x] move integration tests to Software Developer Kit minimizing all impact on contracts and other services)

Output:

• [x] A strategy is made around how this is going to be done
• [x] Strategy is reviewed by whole dev team before implementation start

[theblockstalk]

>> = move -->> = copy

Strategy 1: move minimal functions to SDK Integration/blockchain (docker container + initialization) >> Tonomy Contracts/blockchain Integration/initialize (typescript bootstrap.ts) >> SDK/initialize-blockchain Integration/scripts/helsers.sh test() >> SDK/test.sh Integration/scripts/helpers.sh init() to now use Tonomy Contracts/blockchain Integration/test >> SDK/integration-test Integration/docker-compose -->> SDK/test.sh as a docker command which also initializes, from Tonomy Contracts/blockchain

SDK CI for integration test = run the test.sh command

[theblockstalk]

Strategy 2: multi-stage docker container Integration/blockchain (docker container + initialization) >> Tonomy Contracts/blockchain Integration/initialize (typescript bootstrap.ts) >> SDK/initialize-blockchain Integration/scripts/helsers.sh test() DELETE Integration/scripts/helpers.sh init() to now use Tonomy Contracts/blockchain Integration/test >> SDK/integration-test Integration/docker-compose -->> SDK/integration-tests/Dockerfile

Pros

• tests are more sandboxed and repeatable. less errors for devs

Cons

• no debugging of integration tests

Tonomy Contracts/blockchain Dockerfile

FROM eosio/eosio:v2.0.13

# setup Antelope node

RUN nodeos\
    -e\
    -p eosio\
    --data-dir /data/data-dir\
    --config-dir /var/config\
    --disable-replay-opts &
    # run in background

# intialize with initialize-blockchain.sh
# stop nodeos gracefully

CMD nodeos\
    -e\
    -p eosio\
    --data-dir /data/data-dir\
    --config-dir /var/config\
    --disable-replay-opts

SDC/integration-tests Dockerfile

FROM Tonomy Contracts/blockchain/Dockerfile

# install nodejs on same node manually, as we need to run nodeos

# initialize with bootstrap.ts

# run integration tests

SDK CI for integration test = run docker build command

[theblockstalk]

talked with @Rebal67. Agreed to go with Strategy 2

• both strategies: initialize the docker container with initalize.sh
• COPY command will skip if no change
• how to set FROM / BASE dockerfile from another Docker file? maybe need to research
• use VS Code extension to allow debugging of integration tests within Docker container
• run test with docker build or docker run with volume of repo? ideally with docker run ...
• probably need to extend the blockchain file and install nodejs manually

[theblockstalk]

TODO

• [x] Integration/blockchain (docker container + initialization) >> Tonomy Contracts/blockchain
• [x] Integration/initialize (typescript bootstrap.ts) >> SDK/initialize-blockchain
• [x] Integration/scripts/helsers.sh test() DELETE
• [x] Integration/scripts/helpers.sh init() to now use Tonomy Contracts/blockchain
• [x] Integration/test >> SDK/integration-test
• [x] Integration/docker-compose -->> SDK/integration-tests/Dockerfile
• [x] try VS code extension
• [x] update README.md incl dependancies

[theblockstalk]

follow up work. create tasks for

• [ ] currently SDK has different typescript/jest configurations/run scripts (jest/tsdx) for
  • /initialize-blockchain
  • /test-integration
  • /test
  • /src
  • id.ts (cli.tsconfig.json)
• [x] unit tests for SDK are failing (not because of this work)
• [ ] move SSO repo to be sub of SDK