Test Scenario: Walk the curve segments and quotes on the screen

Table of Contents

This page documents a test scenario verifying Draw the nested collections of a curve entry in Standardise the curve configuration's parameters on the one contract. 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 environment is ready. The database was recreated from this commit, the 24 services run, and the Acme Corporation tenant is provisioned with no failed step. The tenant holds four curve configurations; the UK one carries seventeen yield curves across YieldCurves, and eighteen sections hold no curve in that document. Every yield curve holds one segment of kind Simple with twelve quotes.

Open the shell in the tenant administrator's session:

./compass.sh open-as tenant_admin

2. Scenario Info

Field Value
Verifies task Draw the nested collections of a curve entry
Parent story Standardise the curve configuration's parameters on the one contract
Target screen Reporting, Curve configurations (/reporting/curve-configurations)
Clients  
State PASSED

The numbers this scenario states were measured on a fresh provisioning of the branch it was written against. A later dataset changes them; treat a count that moved as information, and a count that moved to zero as a failure.

3. Steps

3.1. Log in as the tenant administrator

  • Run ./compass.sh open-as tenant_admin.
  • The sign-in page shows tenant_admin@acme_corporation and the password Secure-Password-123. Press Sign in.
  • If the shell asks which party to work as, choose Acme Corporation Plc.
  • Pass: the home page opens with Welcome, Tenant Admin, working for Acme Corporation Plc, and no error notice.

3.1.1. Result

Field Value
Status PASS

3.2. Open the UK curve configuration

  • Go to Reporting and choose Curve configurations.
  • Pass: the list holds four configurations: Group, HK, UK and US curve configuration.
  • Click UK curve configuration.
  • Pass: the page title is UK curve configuration, the tabs are Details, Curves, Used by and History, and the line under the title reads Version 1 · 289 of 289 parameters carry documentation from the ORE parameter contract.

3.2.1. Result

Field Value
Status PASS

3.3. Read the segments of a curve

  • Click the Curves tab.
  • Pass: the rail on the left shows YieldCurves holding 17 curves, and one line 18 sections hold no curve in this document.
  • Pass: GBP1D is selected, and the workbench shows its header, then The curve, then Its parameters.
  • Scroll to the card titled Its Segments.
  • Pass: the card says 1 row, and the row names its kind: Simple.
  • Pass: the row lists the five leaves a Simple segment reads, each with a value or a default and a Documentation link: Conventions with GBP-OIS-CONVENTIONS, Pillar choice with Default: LastRelevantDate., Priority with Default: 0., Minimum distance with Default: 1., and Projection curve reading Default: Not given. ORE applies its own rule.
  • Note: a dash instead of a default means the leaves were not curated, and the snag recorded below is back.
  • Note: a snag is a segment leaf that prints an ORE name such as Conventions or RecordedAt where a label belongs, or a leaf that belongs to another kind.

3.3.1. Result

Field Value
Status PASS

3.4. Confirm the segment's quotes

  • Still on the Its Segments card, below the leaves.
  • Pass: the line reads 12 quotes.
  • Pass: twelve identifiers follow, in tenor order, all of the form IR_SWAP/RATE/GBP/0D/1D/…: 1M, 3M, 6M, 12M, 2Y, 3Y, 5Y, 7Y, 10Y, 15Y, 20Y and 30Y.
  • Note: a snag is a quote listed under the wrong segment, a quote missing, or the list ordered by anything other than tenor.

3.4.1. Result

Field Value
Status PASS

3.5. Confirm what the page does not draw

  • At the foot of the workbench, below the parameters and the segments.
  • Pass: a card titled Other elements it can hold lists them, one to a line, each with its state on the right: Report with not set, and BootstrapConfig with this screen cannot read it yet.
  • Pass: Segments does not appear in that card, because the page draws the segments as rows and naming the block again would say it twice.

3.5.1. Result

Field Value
Status PASS
Notes "Held as its own element:; Report; not stated; BootstrapConfig; not recorded here" this is extremely confusing to users.

3.6. Read the Details tab

  • Click Details.
  • Pass: the card shows the configuration's name, its version, the party that holds it, the count of curves and the documentation count.
  • Pass: a sentence says what the configuration decides (each curve's definition and bootstrap) and what it does not (the market a run reads, nor the trade data).

3.6.1. Result

Field Value
Status PASS

3.7. Read the reports the configuration serves

  • Click Used by.
  • Pass: a table lists the reports bound to this configuration with the party that runs them, under ACME Corporation UK plc: Audit Trail Summary, Bucketed DV01, Cashflows, Credit Curves, CVA/DVA/FV.
  • Pass: the sentence above the table says a change reaches the next run of each report, and that a run already produced keeps what it ran with.

3.7.1. Result

Field Value
Status PASS

3.8. Read the history of the configuration

  • Click History.
  • Pass: the newest version comes first, dated, reading Created with the reason code system.external_data_import for a freshly provisioned configuration.
  • Pass: a Hide system activity control is shown.
  • Note: an empty history, or a timeline with no version, is a failure: the curve configuration's history provider has to be registered for the page to draw it.

3.8.1. Result

Field Value
Status PASS

3.9. Check the known snags

These are the defects already recorded. Meeting one is expected; the step is to confirm the current behaviour and say whether it is what the note describes.

  • Pass: Conventions draws with its label and its value GBP-OIS-CONVENTIONS, and a Documentation link. A gap here means the build predates the inherited leaves, the task that closed it.
  • Pass: the GBP1D header reads 10 parameters while the page reads 238 of 238, because the curve's tag counts its own parameters and not its segment's. Still open; it is a snag, not a failure of this walk.
  • Pass: no row reads RecordedAt. A row that shows it means the build predates the fix.
  • Pass: PillarChoice, Priority and MinDistance draw their defaults and the entry carries no without documentation line, so the page reads 289 of 289. They were curated by Curate the shared segment leaves; a dash here means the contract lost their rows.

3.9.1. Result

Field Value
Status PASS

4. Results

Field Value
Status PASSED
Completed at 2026-10-30T17:56:00Z
Branch main at 9b358a3bf4, on a database recreated and an Acme tenant provisioned for this walk
Evidence the UK workbench,

the segment card after the curation |

Commit 9b358a3bf4
Worktree ores_dev_merry_newton

5. Notes

Emacs 29.3 (Org mode 9.6.15)