Contact Details
meryemefe from Slack
Describe the feature
Instead of storing each testcase as a run and testcase information, we can store testcase information separately and store testCaseRun as another table.
Therefore, the following changes are proposed:
- Instead of current test_case table, we created a new test_case table which stores columns for test definition such as repository_id, suite_name, class_name, test_name.
- Created test_case_run table which keeps test case results for each workflow run.
- Existing test_suite is renamed as test_suite_run for consistency.
- test_case_flakiness is removed and the fields are moved to new test_case table.
- In test_case_statistics table, we use test_case_id as FK instead of keeping repository_id, suite_name, class_name, test_name columns again.
Here is the ER diagram of proposed solution.
Contact Details
meryemefe from Slack
Describe the feature
Instead of storing each testcase as a run and testcase information, we can store testcase information separately and store testCaseRun as another table.
Therefore, the following changes are proposed:
Here is the ER diagram of proposed solution.