Test Scenario: Capture the sprint 29 release screenshots

Table of Contents

This page documents a test scenario verifying Sprint 29 in Sprint 29. 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 before you open this scenario.

  • Worktree jolly_knuth runs a current build of main.
  • The database is recreated and acme_corporation is provisioned.
  • The services run.

Rules for every capture:

  • Use the light theme and English unless the step says otherwise.
  • Use a browser window 1600 pixels wide, at 100% zoom.
  • Save each image in assets/images/ with the file name the step gives.
  • Do not capture real names, passwords or tokens.

2. Scenario Info

Field Value
Verifies task Sprint 29
Parent story Sprint 29
Target screen The web client screens named in each step
Clients  
State PASSED

3. Steps

Each step captures one image for the release notes. Record PASS, FAIL or PENDING in its *** Result. Record FAIL when the screen is empty, shows an error or does not match the step, and say what you saw.

3.1. Log in as tenant_admin

  • Open http://localhost:20802/login.
  • Log in as tenant_admin@acme_corporation with the password Secure-Password-123.
  • Confirm that the shell opens with no permission errors.

3.1.1. Result

Field Value
Status PASS

3.2. Capture the trade blotter

  • Open http://localhost:20802/trading/blotter.
  • Select a book node in the rail that holds trades.
  • Confirm that rows show and that the rail states the row counts.
  • Save the screenshot as assets/images/ore_studio-v0.0.29-blotter.png.
  • Caption for the release notes: The trade blotter reads a page at a time, and its rail counts the rows at each node.

3.2.1. Result

Field Value
Status PASS
Notes scenario_capture_the_sprint_29_release_screenshots_step2_20261108_215555.png; ; scenario_capture_the_sprint_29_release_screenshots_step2_20261108_215611.png

3.3. Capture a trade booked as draft

  • Open http://localhost:20802/trading/trades/new.
  • Fill in enough of the form to show a draft trade.
  • Do not submit the trade unless the draft needs it to show.
  • Save the screenshot as assets/images/ore_studio-v0.0.29-trade-draft.png.
  • Caption for the release notes: A trade books as a draft.

3.3.1. Result

Field Value
Status PASS
Notes scenario_capture_the_sprint_29_release_screenshots_step3_20261108_215711.png

3.4. Capture a structure

  • Open http://localhost:20802/trading/structures.
  • Open one structure if the list holds any.
  • Record FAIL if the list is empty.
  • Save the screenshot as assets/images/ore_studio-v0.0.29-structures.png.
  • Caption for the release notes: A structure completes from a screen.

3.4.1. Result

Field Value
Status PASS
Notes scenario_capture_the_sprint_29_release_screenshots_step4_20261108_220508.png; ; ; scenario_capture_the_sprint_29_release_screenshots_step4_20261108_220546.png

3.5. Capture the Connectivity screen

  • Open http://localhost:20802/market-data/connectivity.
  • Show the delivery tree with its publishers and suppliers.
  • Save the screenshot as assets/images/ore_studio-v0.0.29-connectivity.png.
  • Caption for the release notes: Connectivity shows the delivery tree of suppliers, sessions and feeds.

3.5.1. Result

Field Value
Status PASS
Notes scenario_capture_the_sprint_29_release_screenshots_step5_20261108_220613.png; ; ; ; scenario_capture_the_sprint_29_release_screenshots_step5_20261108_220632.png; scenario_capture_the_sprint_29_release_screenshots_step5_20261108_220657.png

3.6. Capture the Public rates screen

  • Open http://localhost:20802/market-data/public-rates.
  • Show the publishers with their freshness.
  • Save the screenshot as assets/images/ore_studio-v0.0.29-public-rates.png.
  • Caption for the release notes: Public rates shows each publisher and its freshness.

3.6.1. Result

Field Value
Status PASS
Notes scenario_capture_the_sprint_29_release_screenshots_step6_20261108_220722.png; ; ; scenario_capture_the_sprint_29_release_screenshots_step6_20261108_220742.png

3.7. Capture the fixing series

  • Open http://localhost:20802/market-data/fixings?uri=oresmd%3A%2F%2Ffx%2FEUR%3Ftype%3Dfixing%26index%3Dfx%26source%3DECB%26ccy%3DCNY.
  • Open a series with history if one exists.
  • Record FAIL if no fixings exist.
  • Save the screenshot as assets/images/ore_studio-v0.0.29-fixings.png.
  • Caption for the release notes: Public fixings are published through an adapter.

3.7.1. Result

Field Value
Status PASS
Notes scenario_capture_the_sprint_29_release_screenshots_step7_20261108_221042.png

3.8. Capture the synthetic feeds

  • Open http://localhost:20802/market-data/synthetic.
  • Open a running feed if the tree holds one.
  • Save the screenshot as assets/images/ore_studio-v0.0.29-synthetic-feeds.png.
  • Caption for the release notes: Synthetic feeds, with the richer tick arrival models.

3.8.1. Result

Field Value
Status PASS
Notes scenario_capture_the_sprint_29_release_screenshots_step8_20261108_221102.png; ; scenario_capture_the_sprint_29_release_screenshots_step8_20261108_221117.png; ; ; ; scenario_capture_the_sprint_29_release_screenshots_step8_20261108_221148.png

3.9. Capture a convention record

  • Open http://localhost:20802/refdata/conventions.
  • Open one family, then one convention.
  • Show the record page with its sections.
  • Save the screenshot as assets/images/ore_studio-v0.0.29-convention.png.
  • Caption for the release notes: A convention is drawn to the one standard for ORE leaves.

3.9.1. Result

Field Value
Status PASS
Notes scenario_capture_the_sprint_29_release_screenshots_step9_20261108_221220.png; ; ; ; scenario_capture_the_sprint_29_release_screenshots_step9_20261108_221234.png; scenario_capture_the_sprint_29_release_screenshots_step9_20261108_221246.png

3.10. Capture a curve configuration

  • Open http://localhost:20802/reporting/curve-configurations.
  • Open one configuration.
  • Show the same list and record layout as the other configurations.
  • Save the screenshot as assets/images/ore_studio-v0.0.29-curve-configuration.png.
  • Caption for the release notes: Curve configurations follow the one configuration screen standard.

3.10.1. Result

Field Value
Status PASS
Notes scenario_capture_the_sprint_29_release_screenshots_step10_20261108_221314.png; ; ; scenario_capture_the_sprint_29_release_screenshots_step10_20261108_221327.png; scenario_capture_the_sprint_29_release_screenshots_step10_20261108_221339.png

3.11. Capture a currency record

  • Open http://localhost:20802/refdata/currencies.
  • Open USD.
  • Show the record page from the screen pipeline.
  • Save the screenshot as assets/images/ore_studio-v0.0.29-currency.png.
  • Caption for the release notes: Currencies went through the screen pipeline.

3.11.1. Result

Field Value
Status PASS
Notes scenario_capture_the_sprint_29_release_screenshots_step11_20261108_221400.png; ; ; scenario_capture_the_sprint_29_release_screenshots_step11_20261108_221415.png

3.12. Capture the dark theme

  • Open http://localhost:20802/refdata/currencies.
  • Switch to the dark theme from the header.
  • Open the language menu in the header, so that it shows in the image.
  • Return to the light theme after the capture.
  • Save the screenshot as assets/images/ore_studio-v0.0.29-dark-theme.png.
  • Caption for the release notes: The interface switches between light and dark and chooses its language from the header.

3.12.1. Result

Field Value
Status PASS
Notes scenario_capture_the_sprint_29_release_screenshots_step12_20261108_221441.png; ; ; scenario_capture_the_sprint_29_release_screenshots_step12_20261108_221450.png

3.13. Capture the release hero image

  • Open http://localhost:20802/operations.
  • Show a populated overview.
  • Choose the screen you think best represents the release, if another is better.
  • Save the screenshot as assets/images/ore_studio-v0.0.29-hero.png.
  • Caption for the release notes: ORE Studio at the end of sprint 29.

3.13.1. Result

Field Value
Status PASS
Notes scenario_capture_the_sprint_29_release_screenshots_step13_20261108_221511.png; ; ; scenario_capture_the_sprint_29_release_screenshots_step13_20261108_221550.png; ; ; scenario_capture_the_sprint_29_release_screenshots_step13_20261108_221608.png

4. Results

Field Value
Status PASSED
Completed at 2026-11-08T22:16:16Z
Branch  
Commit  
Worktree  

5. Notes

  • No web route exists for volatility surfaces or for the product type page, so this scenario has no step for them.
  • The streaming work has no still image. A short recording of a list that updates by itself shows it better.
  • After the captures, add each image and its caption to the release notes, then export the notes and update the draft release.

Emacs 29.3 (Org mode 9.6.15)