☀️ Initial setup best practices

Review the recommended initial setup best practices below to make sure you get the most value out of the features and functionality Helios has to offer.

Go

Java

Node.js

Python

Ruby

Minimum version supported by Helios

1.17

8

10

3.6

2.7

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

Go
Java
Node.js
Python
Ruby

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

Install the Helios Slack app (under user menu > Settings > Integration > Slack) to get reports and alerts directly to your selected Slack channel.

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.


Did this page help you?