Test Scenario: Run a report and read its rows
This page documents a test scenario verifying Run a report from its page and read its rows in Prove the report grid run end to end — the remaining work. It is filled in with the target screen and checklist of steps before testing starts; record the outcome by hand in * Results.
1. Before you start
- The database is the environment's own, provisioned with Acme Corporation
holding group:
compass db status answers, and the fleet is up with
compass services status showing every unit running, including the five
ores.compute.wrapper nodes.
- The report the scenario runs has market data for the date it prices at. A fresh
environment carries no currency curve quotes, so seed them first with
How do I seed currency quotes for a local report run?.
Without them the run reaches the grid and the engine refuses every curve.
- The result rows table answers the reporting service:
grant select, insert, update, delete, truncate on
ores_reporting_report_result_rows_tbl to ores_swift_curie_reporting_service
is applied, which a freshly recreated database grants through its prefix grant
function.
- Open
http://127.0.0.1:20202 and sign in as
tenant_admin@acme_corporation / Secure-Password-123, then choose the party
ACME Corporation HK Ltd in the party picker.
3. Steps
3.1. Log in as the tenant administrator
- Sign in at
http://127.0.0.1:20202 as tenant_admin@acme_corporation with
the password Secure-Password-123.
- Choose the party
ACME Corporation HK Ltd in the party picker at the top.
- Confirm the
Reporting area appears in the main navigation.
3.2. Open the NPV report definition
- Go to
Reporting then Reports.
- Open the report named
NPV.
- Confirm the page states the definition first, with the tabs
Definition and
Runs, and that Run and Refresh sit at the top right.
3.3. Start the run from the definition
- Press
Run.
- Confirm the page moves to a new run's page, with the tabs
Run and
Results.
- Confirm the run's state moves from
queued or running without the page
being reloaded by hand.
3.4. Follow the run to the grid
- On the run's
Run tab, confirm the run names its compute batch and that the
state moves through the pipeline rather than resting in one state.
- Open
Operations then the compute area, and confirm the batch and its jobs
are listed for this run, and that the jobs reach Done.
- Return to the run's page and confirm its state is
completed.
3.5. Read the run's results
- Open the run's
Results tab.
- Confirm the header states the number of trades and the priced date, and that
one row per trade is drawn.
- Confirm the note says the rows are the ones the post-processor loaded, not the
engine's file.
- Change
Aggregate by to Book and confirm the books roll up under their
portfolios, then to Counterparty and confirm the rows roll up by
counterparty.
3.6. Check the rows in the store
- In a shell, run
compass sql -- -c "set row_security=off; select measure, count(*) from ores_reporting_report_result_rows_tbl group by 1;".
- Confirm the run's rows are there with the measures the report produced, and
that the count matches the trades on the screen times the measures.
- Confirm
select count(*) from ores_reporting_report_result_rows_tbl equals
the rows the screens draw and not a row more.
4. Results
| Field |
Value |
| Status |
PASSED |
| Completed at |
2026-10-27T20:17:57Z |
| Branch |
|
| Commit |
|
| Worktree |
|
5. Notes
Emacs 29.3 (Org mode 9.6.15)