☀️ Initial setup best practices

The first step in the initial setup is to share the relevant dependencies file with the Helios team by emailing [email protected].

	Node.js	Python
Dependencies file	`package.json`	`requirements.txt`
Minimum version supported by Helios	10	3.6

Once the dependencies are confirmed, you may proceed and perform the initial setup and add some services, existing tests and logs to Helios.

Installation (adding to Helios)	Benefits	Validation that setup is done	Guide
Service	✅ Real-time visibility into what's happening in your local environment ✅ Generate triggers and tests ✅ Access trace visualization	👍 Traces from the service show up in the Helios app and trace visualization can be used 👍 A trigger can be uploaded into Postman 👍 Service commit hash from CI environment shows up in trace visualization	Node.js Python
Tests	✅ Real-time visibility into rest runs and results, including changes over time ✅ Easier debugging using visualization	👍 Tests & tests runs (traces) show up in the 'Tests' page 👍 URL to test run (trace) visualization is printed in the console at the end of each test run 👍 Test runs show (and link to) job name and ID from CI environment	Cucumber Cypress Jest Mocha pytest Identifying test runs in CI environment
Logs	✅ 1-click access to trace visualization in Helios directly from your logs	👍 URL to trace visualization in Helios is easily accessible from each log	logz.io

Installation (adding to Helios)

Benefits

Validation that setup is done

Guide

Service

✅ Real-time visibility into what's happening in your local environment
✅ Generate triggers and tests
✅ Access trace visualization

👍 Traces from the service show up in the Helios app and trace visualization can be used

👍 A trigger can be uploaded into Postman

👍 Service commit hash from CI environment shows up in trace visualization

Tests

✅ Real-time visibility into rest runs and results, including changes over time
✅ Easier debugging using visualization

👍 Tests & tests runs (traces) show up in the 'Tests' page

👍 URL to test run (trace) visualization is printed in the console at the end of each test run

👍 Test runs show (and link to) job name and ID from CI environment

Logs

✅ 1-click access to trace visualization in Helios directly from your logs

👍 URL to trace visualization in Helios is easily accessible from each log

Finally, make sure the mutual Slack channel with Helios and your company is set up (might require admin approval).

👍
All set
That's it! You're all setup and ready to use Helios during your development cycle.