Add trace based testing examples

[danielbdias]

Changes

On this PR, we are adding some examples of Trace-based test cases that can be run against the demo and can be used to validate the traces emitted for each service, discussed on #873.

To do that, we added the tracetest server on the docker-compose.yaml to run tests against the infrastructure and added a set tests for each service on ./test/tracetesting.

You can run these tests manually by running the following command: make run-tracetesting

Merge Requirements

For new features contributions, please make sure you have completed the following
essential items:

• CHANGELOG.md updated to document new feature additions
• Appropriate documentation updates in the docs
• Appropriate Helm chart updates in the helm-charts

Maintainers will not merge until the above have been completed. If you're unsure
which docs need to be changed ping the
@open-telemetry/demo-approvers.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: danielbdias / name: Daniel Baptista Dias (fc1005a, dbedfd6, 5f31c6d, d2d9d06, 32c0e72, d129654, 804ef19, 5eb055a, 4080548, ddd9912, 43a6eeb, b4f896d, c52d03b, 02d7f7b, 2bd7c5f, 6725bbd, 14e2ea6, 5dbcec2, d60eebd, 72d2cdd)

[austinlparker]

Please make sure you sign the CLA

[danielbdias]

Hi everyone! I was able to sign the CLA and fix some of the issues reported by the Github Actions.

In this first part of the PR, I've added four trace-based tests:

• one test simulating a user doing a checkout process;
• three tests porting AVA tests to tracetest, checking both the outcome of the API call and some properties of the traces emitted by it.

Does it make sense to you? If yes, the next two steps that I can do on this PR are:

1. Port the other AVA tests to tracetest, asserting the API outcome and the properties of the traces emitted by the APIs;
2. Build a Github Action that will have the following idea:

# install tracetest on this container
curl -L https://raw.githubusercontent.com/kubeshop/tracetest/main/install-cli.sh | bash

# run services in docker-compose
docker compose up -d --no-build

# run trace-based tests
cd test/tracetesting
./run.bash

Feel free to ask anything and to make suggestions or comments about this PR and how we can improve it.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[danielbdias]

Hi everyone! I updated this PR based on our latest interaction and fixed tracetest version to a RC version (that will be released this week) to solve two things:

1. intermittency that was causing tracetest to not print the test values to the cart test;
2. an update to refer to the protobuf file in the test files instead of embedding it, which made this PR shorten from 7000 lines to 1000.

Feel free to ask anything and to make suggestions or comments about this PR!

[austinlparker]

• This will need to be updated to work with splitting up services into modules #872
• Align trace tests with load generator routes being exercised

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[austinlparker]

Waiting on #872

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[danielbdias]

Hi folks!

I updated this PR to comply with the startup division that will happen on #872 .

The idea of this PR is to divide and have trace-based tests per service that will be triggered on run.bash (ref link).

Today the test runner called all services, but as soon as we have #872 merged, I'll update it to call the available services.

Also, I've updated the tests for the frontend-service to have the same URL calls as the load-generator.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[danielbdias]

I saw that #872 was merged now. I will work on this PR to support it.