App Dashboard
This page lists all the test cases for this feature. Test cases are followed by an explanatory legend.
The dashboard now benefits from complementary automation layers:
- business/data validation through
pytestintests/test_dashboard.py; - user-path and display-format validation through Playwright Chromium in
e2e/src/tests/dashboardGlobal.spec.ts.
🗃️ Test cases
Coverage rate:
| Status | ID | Title |
|---|---|---|
| ● Active | tc-dash01 | Verify total portfolio value calculation (chart) |
| ● Active | tc-dash02 | Verify overall daily performance calculation |
| ● Active | tc-dash03 | Verify display of Top/Flop Performers |
| ● Active | tc-dash04 | Verify "52-Week Analysis" functionality |
| ● Active | tc-dash05 | Verify behavior with an empty database |
| ● Active | tc-dash06 | Verify advanced chart data objects are injected in template context |
| ● Active | tc-dash07 | Verify a retained business block is rendered after dashboard cleanup |
| ● Active | tc-dash08 | Verify cleaned CSV path is used when source file is available |
| ● Active | tc-dash09 | Verify business blocks Gains to secure and Reinforce or liquidate are displayed |
| ● Active | tc-dash10 | Verify dashboard no longer renders milestone distance chart |
| ● Active | tc-dash11 | Verify advanced metrics use CSV without historical dependency |
| ● Active | tc-dash12 | Verify index page renders one gauge per stock with a single global % symbol |
| ● Active | tc-dash13 | Verify gauge marker values are normalized to [-100, +100] bounds |
| ● Active | tc-dash14 | Verify dashboard contract keeps analyst/contrarian signal keys even with sparse data |
| ● Active | tc-dash15 | Verify no cards from legacy specs are accidentally restored in secure dashboard |
| ● Active | tc-dash16 | Verify P/E ratio contract keys keep empty defaults when CSV is unavailable |
| ● Active | tc-dash17 | Verify Top P/E Ratio high card is rendered with expected rows |
| ● Active | tc-dash18 | Verify Top P/E Ratio low card is rendered with expected rows |
| ● Active | tc-dash19 | Verify P/E cards keep reference visual classes and performer-list structure |
| ● Active | tc-dash20 | Verify dashboard JSON contract contains trigger counts for retained cards |
| ● Active | tc-dash21 | Verify removed legacy block labels are absent from secure dashboard output |
| ● To Do | Dashboard: Graceful fallback rendering when an internal exception occurs | |
| ● To Do | Mobile Display: Responsive layout check |
ⓘ Coverage status legend
| Status | Description |
|---|---|
| ● Active | The test case is covered by automated validation in pytest, Playwright, or both depending on the nature of the check. |
| ● To Do | The test case is defined but does not yet have a corresponding pytest test. |