Move infrastructure helpers to package

README.md

@@ -72,6 +72,14 @@ NO_DOCKER=1 yarn test # all tests
 ...
 ```
 
+## Development
+
+If you're developing integration tests and need to add additional helper methods to the @neutron-org/neutronjs packages, start by cloning the package repository. Use the command git clone [email protected]:neutron-org/neutronjs.git. After cloning, you have two options: either alter the package reference in the package.json file to point to your cloned repository, or use yarn link.
+
+Once the JavaScript helper code in your local repository is ready, your next step is to create a Pull Request (PR). This PR must be reviewed and approved before it can be merged into the main branch.
+
+However, even after the merge, you cannot immediately use the new package version in your integration tests. First, you need to wait until the updated version of the package will be published to the npmjs repository. After the new version has been published, you can incorporate it into your integration tests. This will allow you to complete the testing sequence in your GitHub Actions workflow.
+
 ## Warning
 
 Since docker-compose doesn't rebuild images on file changing, there is a chance for one to launch the tests with an

globalSetup.ts

@@ -1,7 +1,7 @@
-import { setup } from './src/helpers/env';
+import { env } from '@neutron-org/neutronjsplus';
 
 export default async () => {
   const host1 = process.env.NODE1_URL || 'http://localhost:1317';
   const host2 = process.env.NODE2_URL || 'http://localhost:1316';
-  !process.env.NO_DOCKER && (await setup(host1, host2));
+  !process.env.NO_DOCKER && (await env.setup(host1, host2));
 };

package.json

@@ -39,6 +39,7 @@
     "@cosmos-client/core": "0.45.13",
     "@cosmos-client/cosmwasm": "^0.20.1",
     "@cosmos-client/ibc": "^1.2.1",
+    "@neutron-org/neutronjsplus": "^0.0.9",
     "@types/lodash": "^4.14.182",
     "@types/long": "^4.0.2",
     "axios": "^0.27.2",