feat(core): Keep track of test case executions during test run (no-changelog) #12787
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR introduces a new entity "TestCaseExecution". It represents a specific past execution being "re-run" and evaluated during a specific Test Run.
The idea is to store the connection between Test Runs and related executions (past, new and evaluation) in a separate table, together with statuses, errors, individual metrics produced by the evaluation workflow. This will allow us to keep track of the details of each Test Run even after related executions will be pruned, and make data fetching more efficient and straightforward in general. Previously, we had to rely on a workaround with the
testRunId
property added to each evaluation execution's metadata.Related Linear tickets, Github issues, and Community forum posts
Review / Merge checklist
release/backport
(if the PR is an urgent fix that needs to be backported)