v0.11.7 Testing checklist

[jorgeepc]

Testing Tracetest

This is the entire checklist on what we should do to assert that Tracetest is working fine on each version release. On each version release, we can copy the contents of this template checklist and open a Github Discussion to start each test.

On Tracetest, we work in two ways to test the entire system and guarantee that everything is working fine. One is through automatic tests, where we run unit, integration and end-to-end tests on Tracetest CLI, Web UI and Server.

Another source of tests is the manual tests that we execute on each release, simulating users, and checking if everything is ok on these tests.

Manual Tests

On our manual tests, we aim to do some sanity checks to see if the main features are working as expected. Usually, we run it on each Tracetest release.

Tests to validate on Release Candidate

• Test server installation via CLI

  • Docker Compose and no demo API
  • Docker Compose and demo API
  • Kubernetes and no demo API
  • Kubernetes and demo API
  • Verify that Tracetest is not sending analytics if you have the TRACETEST_DEV env for docker install
  • Verify that Tracetest is not sending analytics if you have the TRACETEST_DEV env for k8s install

• Test DataStore provisioning and basic test

  • Open WebUI and go to /settings page. The provisioned Data Store should be selected
  • Create a test on WebUI that calls a demo API (like Pokeshop or Open Telemetry Store). This test should fetch traces correctly and run without errors

• Test Tracetest examples (probably we could skip this step for the relase)

  • Jaeger example
  • Tempo example
  • New Relic example
  • Lightstep example
  • OpenSearch example
  • Elastic APM example
  • SignalFX example
  • Datadog example
  • Amazon X-Ray example

• Test specific features added/changed on this release:

  • Honeycomb integration. Test the following features: data store provisioning, webUI settings page, cli get | apply datastore command using honeycomb, run a test and validate data is being send to both Tracetest and Honeycomb
  • Validate new CLI environment resource: list environment, apply environment, get environment, delete environment
  • Validate CLI test run command using an environment --environment
  • Validate webUI environment CRUD
  • Validate a test run from the webUI using an environment
  • Validate a transaction run from the webUI using an environment
  • Validate test specs snippets from the webUI

Tests to validate on Final Release

• Pipeline

  • Check if our release pipeline on Release Tracetest workflow on Github Actions worked correctly

• Test CLI updates

  • MacOS via homebrew
  • MacOS via curl script
  • Windows via chocolatey
  • Windows via manual download

• Docs

  • Double check Detailed installation docs and see if everything is documented correctly

• Test specific features added/changed on this release:

  • Add list of features here

Automatic Tests

Today Tracetest has 3 main components: a WebUI, a CLI and a Server.

Web UI

• Unit tests: Run by executing npm test on ./web folder
• End-to-end tests: Run using cypress against a temporary Tracetest created on Kubernetes.

CLI

• Unit tests: Run by executing make test on ./cli folder

Server

• Unit tests: Run by executing make test on ./server folder
• Integration tests: Run along with some unit tests running make test on ./server folder, but also done in a matrix test on Github actions, by executing the test-examples action.
• End-to-end tests: Run using Tracetest to test itself. We deploy two instances of Tracetest and use one to test API calls to another on Github actions, by executing the trace-testing action.

[xoscar]

Found two problems:

1. The tracetest-opensearch example is not able to fetch the trace (not sure if I did something wrong)
2. Using a grpc example when installing Tracetest using the CLI with the pokeshop demo doesn't work, All http examples work tho!

[xoscar]

Found another issue

• when clicking the test connection button when having honeycomb selected the app shows an errored notification

I'm fixing this

[xoscar]

Found another pre-existing bug:

• When running a transaction without an id form the CLI, it doesn't update the id field from the resource file, causing every consecutive run to create a new transaction entry
• Trying to delete a transaction with the above problem causes a foreign key issue in the DB
  

[xoscar]

Found a pre-existing bug with the environment form modal

• When trying to edit an environment by deleting one of the value entries, the update stays as disabled