Test Scenario: Walk the engine settings screens as an Acme user

Table of Contents

This page documents a test scenario verifying Test the engine settings in See and change everything a report runs. 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

Do these steps yourself, in this order, before you open the web client.

  • Build the checkout of feature/test-the-engine-settings, then confirm the schema with compass db status. Recreate the database with compass services stop and compass db recreate -y -k when it says "out of sync".
  • Start the services with compass services start. Check that ores.reporting.service, ores.http.server and ores.web.service run.
  • Provision Acme with compass shell -f projects/ores.shell/scripts/library/provisioning/how_do_i_provision_the_system_with_acme_corporation_holding_group.ores. The run must finish with no failed step.
  • Check that Acme holds engine settings: compass sql -- -c "select name from ores_reporting_engine_settings_tbl where valid_to = ores_utility_infinity_timestamp_fn() order by name" must list seven names, for example UK - Valuation and risk engine settings. If it lists none, the publish of the Acme bundle did not reach the reporting tables. Record this in the notes and stop.
  • Check that the Acme tenant holds the parameter documentation: compass sql -- -c "select count(*) from ores_reporting_ore_parameters_tbl p join ores_iam_tenants_tbl t on t.id = p.tenant_id where t.code = 'acme_corporation' and p.valid_to = ores_utility_infinity_timestamp_fn()". The count must be 610. The base bundle that provisioning publishes carries the parameters and their value domains. If the count is 0, the publish of base did not reach the reporting service. Record this in the notes and stop.
  • Open the web client as the tenant administrator: compass open-as tenant_admin.

Nothing in this scenario was run against a live service before this page was written. A failure can come from the screens, the BFF, the reporting service or the data. Write down which layer you think failed.

2. Scenario Info

Field Value
Verifies task Test the engine settings
Parent story See and change everything a report runs
Target screen Engine settings, at /reporting/engine-settings
Clients  
State PASSED

3. Steps

3.1. Sign in as the tenant administrator

  • Sign in as tenant_admin@acme_corporation. The password is Secure-Password-123. compass open-as tenant_admin fills the form.
  • Select the UK party (ACME Corporation UK plc) when the page asks for a party. Steps 3 to 11 change UK rows, and a row can be changed only in the party that owns it.
  • The sign-in must succeed and show the home page.

3.1.1. Result

Field Value
Status PASS

3.2. Open the engine settings list

  • Open the Reporting area and choose the Engine settings card. The address is /reporting/engine-settings.
  • The title must read "Engine settings". The list must show the columns Name, Party, Groups set, Threads, Changed by and Last changed.
  • The list holds the engine settings of every party the selected party can see. For the UK party, expect "UK - Exposure simulation engine settings" and "UK - Valuation and risk engine settings".
  • Write down the Threads value of each row. Expect 4 for the exposure simulation and 1 for valuation and risk.
  • Switch to the group party (Acme Corporation Plc). The list must now hold the settings of all four parties, and the Party column must say which party owns each row.
  • Choose UK in the party filter. Only the two UK rows must remain. Choose All parties to bring the rest back.

3.2.1. Result

Field Value
Status PASS

3.3. Open the UK valuation and risk settings

  • Open "UK - Valuation and risk engine settings" from the list.
  • The page must show the tabs Details, Fixings and cash flows, Market and trade building, Execution, Used by and History.
  • On Details, the description must state what the settings are for: valuation, risk, regulatory and monitoring reports, one thread per run.
  • Open Execution. Threads must read 1. The log mask must read 31.
  • Open Fixings and cash flows. The setting implyTodaysFixings must read No, and it must not say "default".

3.3.1. Result

Field Value
Status PASS

3.4. Read the documentation of a setting

  • On the Execution tab, choose "Show documentation" on the threads setting.
  • The panel must show a label, a help text, a description and the default. The description must be more than one short sentence.
  • Switch the panel to Advanced. It must show the ORE XML path, the format and the release in which ORE introduced the setting.
  • The text "The documentation of … is not in the data" must not appear. If it appears, the Acme tenant holds no parameter rows. Run the check in "Before you start" again.

3.4.1. Result

Field Value
Status PASS

3.5. Filter the settings

  • On the Execution tab, choose the filter "Set in this configuration". Only the settings with a value must remain, and the count line must change.
  • Choose "Changes the numbers" as well. Only the settings with that mark must remain.
  • Clear both filters. The full list must return.

3.5.1. Result

Field Value
Status PASS

3.6. Change the threads and save

  • On the Execution tab, choose Edit. Change threads from 1 to 2.
  • The page must show "1 change". The control must show the new value.
  • Choose Save. The page must leave edit mode. It must not reload by itself: it still shows the values it read.
  • Refresh must turn gold and pulse four times, because the save made the data change. Its tooltip must say that the data changed.
  • Choose Refresh. The page must show threads as 2, and the time under Refresh must change.
  • The "version" label of the group must rise by one.
  • Open another tab and come back. The tab must not read again and must keep what it showed.
  • Check the database: compass sql -- -c "select n_threads, version from ores_reporting_engine_settings_execution_tbl where valid_to = ores_utility_infinity_timestamp_fn() order by valid_from desc limit 3". One row must show 2.

3.6.1. Result

Field Value
Status PASS

3.7. Refuse a value that is not valid

  • Choose Edit on the Execution tab. Type 0 in the threads field, and then type abc.
  • The page must show a problem text, for example "Threads must be at least 1" or "must be a whole number". Save must not send the value.
  • Choose Cancel or reload. The saved value must stay 2.

3.7.1. Result

Field Value
Status PASS

3.8. Read the history and revert

  • Open the History tab. It must draw the shared timeline: the event chart, the entries grouped by day, one header line for each entry, the note on its own line and a collapsed detail. The newest version of each record carries the "Current version" emblem.
  • The newest entry must be the change to 2 threads. Its detail must show Threads from 1 to 2. The versions that only counted a change of a group must not appear.
  • Choose Revert on an older version of the Execution group. The dialog must say that the values that version held go back as a new version.
  • Confirm. The Execution tab must show the values of that version. The History tab must now hold one more entry, and the old entries must stay.
  • The newest version must offer no Revert.

3.8.1. Result

Field Value
Status PASS

3.9. See the conflict of two editors

  • Open the same configuration in two browser tabs, A and B. Open the Execution tab in both and choose Edit in both.
  • Change threads to 3 in tab A and save.
  • Change threads to 5 in tab B and save.
  • Tab B must show "These settings changed since you opened them" and a "Read again" button. It must not overwrite the value from tab A.
  • Choose "Read again". Threads must read 3.

3.9.1. Result

Field Value
Status PASS

3.10. Check which reports use the settings

  • Open the Used by tab of "UK - Valuation and risk engine settings".
  • The tab must list the reports that bind the settings. The tab must list 22 reports.
  • Open the Execution tab of a configuration that no report binds, once you create one in the next step. The Used by tab must say that no report binds it.

3.10.1. Result

Field Value
Status PASS

3.11. Add, rename and delete a configuration

  • On the list, choose Add. Name it "Scenario test settings". Choose Add.
  • The new page must open. Every group must say that the configuration holds no row and that the engine uses its default.
  • Choose the edit action in the page header and change the name to "Scenario test settings 2". The title must change.
  • Delete the configuration. The dialog must warn that the history is kept.
  • Try to delete "UK - Valuation and risk engine settings". The dialog must refuse and name the number of reports that bind it.

3.11.1. Result

Field Value
Status PASS

3.12. Read a child party's settings from the group party

  • Switch to the group party (Acme Corporation Plc) and open "UK - Valuation and risk engine settings".
  • The page must say that the settings belong to ACME Corporation UK plc, and it must offer "Switch to ACME Corporation UK plc". Edit and Delete must not show on the page header or on a group.
  • Open the History tab. It must say that the history is in the owning party.
  • Choose the switch button. The page must become editable, and the History tab must list the versions.

3.12.1. Result

Field Value
Status PASS

3.13. Read the screens in French

  • Open the account menu and choose Français under Language. Every screen must change at once, and the choice must stay after a reload.
  • Reopen the engine settings page. The title, the tab names and the group titles must show French text, with no raw key such as engineSettings.tabs.history.

3.13.1. Result

Field Value
Status PASS

3.14. Open the screen as a person without write access

  • Sign out. Open a staff member who is not an administrator, for example compass open-as title "senior trader" --location uk.
  • The Engine settings card must show, and the list must read.
  • Record whether the Add and Edit actions show, and whether a save works.
  • A person who works in one party must see no Party column and no party filter on the list.

3.14.1. Result

Field Value
Status PASS

4. Results

Field Value
Status PASSED
Completed at 2026-10-23T23:39:25Z
Branch  
Commit  
Worktree  

5. Notes

  • The Member role holds read and write on the engine settings, so the last step may show the Edit button. That is correct for the seeded role. Record what you see.
  • The screens never ran against a live service before this scenario. Expect defects in the layer between the BFF and the reporting service. Capture each as a task in the story.

Emacs 29.3 (Org mode 9.6.15)