docs: documents the existing outputs

Author: tuliomir

README.md

@@ -23,7 +23,7 @@ If you observe an incorrect behavior while using Hathor headless wallet, see [th
 The Hathor headless wallet is tested automatically with unit tests and integration tests. See the following documentation for more information:
 - [Testing guidelines](/docs/testing.md)
 
-Eventually, some changes to plugins or scripts may require specific testing not covered by those automated tests, but those should be analysed case by case on each PR.
+Eventually, some changes to plugins or scripts may require specific testing not covered by those automated tests, but those should be analyzed case by case on each PR.
 
 ## Contributing
 

docs/testing.md

@@ -47,6 +47,20 @@ On the [`./setupTests-integration.js` file](https://github.com/HathorNetwork/hat
 - All benchmarks files are handled to measure test times
 - The precalculated wallets persistent file is handled between test suites
 
+### Log and debug outputs
+
+All the logs generated by the integration tests are stored in the `tmp/` folder.
+- Each test suite has its own log file named after the suite file name
+- The application logs are stored on the `tmp/app.log` file
+- Other helper logs are stored in their respective files
+
+On the CI context, all logs inside the `tmp` folder are collected and attached to the test run as _artifacts_ for further investigation. On the CI console, only `warn` and `error` logs are printed to avoid cluttering the output.
+
+To find this artifact:
+- Open the GitHub Actions run page
+- Scroll to the bottom and find the `Upload debug transaction logs` section
+- Find the `Artifact download URL` and click it
+
 ### Sequential running
 
 Currently the integration tests must be executed in sequence using the `--runInBand` jest feature. This means many of the tests expects the previous ones to have been run sucessfully and put the network state in a specific condition.