E2E Test Improvements: Aggregate Task Time for Trending Data Across Phases, Tests
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
**What would you like to be added**:
We profile each phase of the CLI execution, tracking the time it takes.
We should have a way to aggregate this data and observe trends in task time based on test, task.
For example, I should be able to ask the question "Is the time it takes to move CAPI from mgmt to workload during an upgrade increasing in Bottlerocket tests" and quickly get an answer.
This could be CW quieries or part of the test tool, or a combination.
**Why is this needed**:
Observe trends in the profiles of individual CLI tasks
Contributor guide
Research direction
Start by examining the existing CLI phase-profiling data and the E2E test tooling that records it. Determine whether aggregation belongs in CloudWatch queries, the test tool, or both; done means answering task-time trend questions by test and task across phases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, kubernetes
- Domain
- cli, observability-sre, performance, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100