Design database structure

[norbertlaposa]

First version:

test_session

• id
• name
• timestamp
• issuer ref user.id
• data

test_session_service

• id
• session_id ref session.id
• name
• url

test_session_service_suite

• id
• test_session_service_id ref test_session_service.id
• name
• url

test_session_service_suite_test

• id
• test_session_service_suite_test_id ref test_session_service_suite_test.id
• name
• url
• type

test_session_service_run

• id
• test_session_service_id ref test_session_service.id
• timestamp
• passed
• failed
• result_log

Simplified version

test_session

• id
• name
• timestamp
• issuer ref user.id
• data

test_session_item

• id
• session_id ref session.id
• service_name
• suite_name
• test_name
• service_url
• suite_url and test_url can be computed by appending suite_name and test_name

test_session_run

• id
• test_session_id ref test_session.id
• test_service_name ref test_session_item.service_name
• timestamp
• passed
• failed
• result_log

[MartinMiksovskyLaposa]

This is the DB structure we put together with @Szkandy back in Feb 2023. This one counts on test versioning, that means it shows the test codebase like in Status page, where you can expand and inspect what actually ran.

I would suggest to not remove this feature and adapt it to Test Cases laters, like in next milestone. Because having "the checklist" for manual test cases & automated tests bodies (codebase) is imo a good info to preserve.

But definitely we can make it light as much as possible atm, to avoid unnecessary difficulties, it's up to you.

[norbertlaposa]

Let's wait for https://github.com/laposa/test-portal/issues/12 before designing db structure.

[norbertlaposa]

Latest version is:

test_session

• id
• name
• timestamp
• issuer ref user.id
• data

test_session_item

• id
• session_id ref session.id
• service_name
• suite_name
• test_name
• service_url

suite_url and test_url can be computed by appending suite_name and test_name

test_session_run

• id
• test_session_id ref test_session.id
• test_service_name ref test_session_item.service_name
• timestamp
• passed
• failed
• result_log