v0.11.10 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

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

• Test specific features added/changed on this release:

  • validate Trace Analyzer settings from webUI. Enable/disable. Update minimum score
  • validate a Test run with the Trace Analyzer enabled. Verify the Trace tab
  • validate a Test run with the Trace Analyzer disabled. Verify the Trace tab
    • ux issue: Avoid showing Analyzer results when I disable it on settings page #2633
  • validate a Test run (with specs) that passes the minimum score in the Trace Analyzer
    • bug: Cannot add specs in WebUI when a test failed in the linter #2634
  • validate a Test run (with specs) that fails the minimum score in the Trace Analyzer
    • bug: Tests specs are not shown if a test fails in linter #2636
  • enable/disable ssl cert verification in test trigger feat: enable/disable ssl cert verification in test trigger #2521
  • flag and parameter validations for CLI apply command feature(cli): adding flag and parameter validations for commands #2600
  • flag and parameter validations for CLI configure command feature(cli): adding flag and parameter validations for commands #2600
  • flag and parameter validations for CLI delete command feature(cli): adding flag and parameter validations for commands #2600
  • flag and parameter validations for CLI get command feature(cli): adding flag and parameter validations for commands #2600
  • flag and parameter validations for CLI list command feature(cli): adding flag and parameter validations for commands #2600
  • flag and parameter validations for CLI server install command feature(cli): adding flag and parameter validations for commands #2600
  • validate All gRPC Spans: Status is Ok test spec snippet fix(frontend): fix grpc test spec snippet #2605
  • validate server and cli version match feature(cli): adding server and cli version match #2598
  • validate protobuf file path reference on Test yaml from CLI feat(cli): Allow user to reference protobuf file path on Test yaml from CLI #2620

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.

[jorgeepc]

Bug list

• Minor bug in cli tracetest configure: [cli] configure command with incorrect endpoint flag shows empty Version message #2632
• tracetest server install not using param validations: [cli] server install command not using validations from cli/parameters/installer.go file #2635 2635
• Cannot add specs in WebUI when a test failed in the linter #2634
• Avoid showing Analyzer results when I disable it on settings page #2633
• Tests specs are not shown if a test fails in linter #2636

[xoscar]

The temporary root span bug issue

#2637

[danielbdias]

Error on tracetest test run: #2645