Test Scenario: Verify CIR/OU/GMM process rename

Table of Contents

This page documents a test scenario verifying Rename CIR, OU, and GMM processes to their proper names in IR Rates synthetic data: dataset seeding, index cleanup, dual-curve, quoting conventions. It is filled in with the target dialog and checklist of steps before testing starts; the QA Validation Runner panel rewrites * Results in place on save.

Scenario Info

Field Value
Verifies task Rename CIR, OU, and GMM processes to their proper names
Parent story IR Rates synthetic data: dataset seeding, index cleanup, dual-curve, quoting conventions
Target dialog IrCurveEditor — Menu: Market Data > Synthetic > Market Simulator (right-click a feed's IR Curves row > Add, or the toolbar's "New IR Curve" action)
Clients  
State PENDING

Steps

Each step is its own heading — the title should be five to seven words so it fits on one line in the QA Validation Runner's step list without wrapping or truncating (e.g. "Edit and save the record", not a full sentence describing the whole operation). The body below the title is a bullet-point checklist, not a prose paragraph: give the tester every piece of context needed to execute that one step without looking anything up elsewhere — what UI state must already exist, exactly what to click or type, and exactly what confirms the step passed. The panel writes each step's PASS/FAIL/PENDING outcome and notes back as a *** Result child heading directly under it.

Connect to tenant Barclays Plc

  • Log in as tenant_admin@barclays_plc / Secure-Password-123 and select BARCLAYS PLC.

Result

Field Value
Status PASS

Open Market Simulator and the seeded curves

  • Menu: Market Data > Synthetic > Market Simulator.
  • Expand the Barclays feed's IR Curves node and verify the seeded curves (the 2026 Realistic archetype rows) are listed, each currently using the Cox-Ingersoll-Ross engine.

Result

Field Value
Status PASS

Reopen a seeded CIR curve config

  • Double-click any row (or select + Edit) to reopen its IrCurveEditor detail dialog.
  • On the Process tab, verify the Engine combo displays "Cox-Ingersoll-Ross" (a spelled-out label), not the raw code COX_INGERSOLL_ROSS or the old CIR.
  • Hover the combo and verify its tooltip reads the Cox-Ingersoll-Ross formula description (dr = κ(θ−r)dt + σ√r dW …).
  • Verify the Sample short-rate paths chart renders without error.

Result

Field Value
Status PASS

Create a new curve with Cox-Ingersoll-Ross

  • Click Add to open a blank IrCurveEditor.
  • Fill in currency, index, source, and a valid tenor template; on the Process tab select "Cox-Ingersoll-Ross" from the Engine combo.
  • Save. Verify the new row appears in the list.

Result

Field Value
Status PASS

Read the created record back

  • Reopen the just-created record's detail dialog.
  • Verify every field round-trips, including the Engine combo still showing "Cox-Ingersoll-Ross" selected.

Result

Field Value
Status PASS

Update the record's engine

  • In the reopened dialog, change the Engine combo to "Vasicek", adjust kappa/theta/sigma to valid values for that engine, and save.
  • Verify the list refreshes showing the new engine and a change reason was recorded.

Result

Field Value
Status PASS

Delete the created record

  • Select the record created above and delete it.
  • Verify it disappears from the list.

Result

Field Value
Status PASS

Verify history shows all changes

  • Open the History dialog for the deleted record (via the list's History action, or the record's audit trail if still addressable).
  • Verify Create (Cox-Ingersoll-Ross), Update (Vasicek), and Delete are all present with correct change reasons and no raw CIR=/=OU codes leaking into any displayed field.

Result

Field Value
Status PASS

Verify FX engine combo shows Ornstein-Uhlenbeck

  • Menu: Market Data > Synthetic > Market Simulator; expand the Barclays feed's FX Rates node.
  • Reopen any seeded FX config (double-click a row), or use the "New FX Rate" action to add one; on the Behaviour tab select the Ornstein-Uhlenbeck engine from the combo.
  • Verify the combo shows "Ornstein-Uhlenbeck" (not the raw ou code) and the field relabelling (κ/σ tooltips mentioning Ornstein-Uhlenbeck) behaves as before the rename.

Result

Field Value
Status PASS

Results

Field Value
Status PASSED
Completed at 2026-07-26T11:14:10Z
Branch feature/rename-cir-to-cox-ingersoll-ross
Commit bf7795117
Worktree merry_newton

Notes

Emacs 29.3 (Org mode 9.6.15)