need help in database design for test case management system

To explain the current database design, a project has many components, and each component has many test case details. test_status table is when a test case is made, it will need to be checked first and be approved by the test checker.(Tester is the one who create the test case, and another user approves the test case) This is the process of creating a new test case.

Moving forward, I'm having a hard time on the SmokeTest part. In smoketest, a user executes the test cases created and logs whether the test case is pass/failed/pending.(test_case_detail table is where a procedure is stored and user executes it). To explain, a project has many release, and per release, you need to smoketest it on different browsers. (a user can add/delete browsers)

Every project release, you need to select test cases from test_case_detail table to include in that release. the scenario is: A user selects a project, then selects a release, then selects a browser, then test cases on that release and is seperated by different components.(a component is a group of test cases) A user will select a component he likes to smoketest. after selecting a component, test cases in that component should show up and a user will log whether a test case is pass/fail/pending.

How can I create a database design where i can create a summary per release? How can I count how many test cases passed on that release. I'm confused because there are many things that you should consider. i should generate a summary per release/browser. Every release has different test cases and so on.