Skip to content
This repository has been archived by the owner on Feb 15, 2022. It is now read-only.

Increase E2E test granularity #492

Open
wrijeff opened this issue Apr 8, 2021 · 0 comments
Open

Increase E2E test granularity #492

wrijeff opened this issue Apr 8, 2021 · 0 comments
Labels
maintenance Chores that need to be done

Comments

@wrijeff
Copy link
Contributor

wrijeff commented Apr 8, 2021

Currently we have two end-to-end tests: one to test raw span processing and one to test the service map.

While adding new usecases (first peer forwarding, now trace group ES callbacks), we've updated the existing tests to cover new functionality. From #480, we should increase test granularity by splitting the current test into more feature-specific tests.

End state would be tests for:

  1. Basic span test - Single DP
  2. Basic service map test - Single DP
  3. Peer Forwarder plugin test - Two DP with forwarding enabled
  4. TraceGroup plugin test - Two DP without forwarding

etc.

This will make it easier to isolate breaking changes based on the specific test failing.

@wrijeff wrijeff added the maintenance Chores that need to be done label Apr 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
maintenance Chores that need to be done
Projects
None yet
Development

No branches or pull requests

1 participant