github workflow: test new chain setup

query-node/kill.sh

@@ -4,14 +4,10 @@ set -e
 SCRIPT_PATH="$(dirname "${BASH_SOURCE[0]}")"
 cd $SCRIPT_PATH
 
-set -a
-. ../.env
-set +a
-
 # Only remove query-node related services
-docker-compose rm -vsf processor
-docker-compose rm -vsf graphql-server
-docker-compose rm -vsf indexer
-docker-compose rm -vsf hydra-indexer-gateway
-docker-compose rm -vsf redis
-docker-compose rm -vsf db
+docker-compose -f ../docker-compose.yml rm -vsf processor
+docker-compose -f ../docker-compose.yml rm -vsf graphql-server
+docker-compose -f ../docker-compose.yml rm -vsf indexer
+docker-compose -f ../docker-compose.yml rm -vsf hydra-indexer-gateway
+docker-compose -f ../docker-compose.yml rm -vsf redis
+docker-compose -f ../docker-compose.yml rm -vsf db

tests/network-tests/run-tests.sh

@@ -36,8 +36,8 @@ yarn workspace api-scripts tsnode-strict src/status.ts | grep Runtime
 # First scenario..
 ./run-test-scenario.sh $1
 
-# In between pickup generated keys from first scenario or bootstrap scene will all well known
-# keys for roles and members..
+# In between pickup generated keys from first scenario or bootstrap scene with all well known
+# keys for workers and members..
 
 # Second scenario..
 # ./run-test-scenario.sh $2

tests/network-tests/test-setup-new-chain.sh

@@ -19,5 +19,4 @@ sleep 3
 yarn workspace api-scripts tsnode-strict src/status.ts | grep Runtime
 
 # Init chain state
-echo 'executing scenario'
 ./run-test-scenario.sh setup-new-chain