v0.11.14 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
  • Azure Application Insights

• Test CLI commands (detailed list here)

  • Tests and Test Runner
  • Resources: Config
  • Resources: Data Store
  • Resources: Demo
  • Resources: Environment
  • Resources: PollingProfile
  • Resources: Transactions

• Test specific features added/changed on this release:

  • (web) Analyzer show only errors filter on Trace tab
  • (web) Analyzer score summary in test list and testRun list
  • (web) Create test spec from duration in trigger response data
  • (web) Validate GRPC status code response for a test with GRPC trigger
  • (web) Environment CRUD feat: add upsert method and enable it for environments #2746
  • (web) Test execution deep link feature(frontend): Adding Test Execution Deep Link #2747
  • (cli) Analyzer resource CRUD

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

[jorgeepc]

Bugs

• [cli] get transaction with pretty output does not return last run info #2760
• [cli] Steps field from list transaction is incorrect #2761