Test Scenario: Export a pricing engine configuration as ORE XML

Table of Contents

This page documents a test scenario verifying Export a pricing engine configuration as ORE XML in Make every configuration screen follow one standard. Run it on the provisioned environment and record each step's outcome in its own table.

1. Before you start

These are yours to run before the tester opens the browser. Do not hand them to the tester.

  • Confirm the environment matches this checkout. compass db status shows the fingerprint in sync; if it is stale, run compass db recreate -y -k.
  • Start the fleet and confirm 24 services are active. compass services status.
  • Provision the tenant if it is not there, and confirm no step failed.
  • Confirm xmllint is on the tester's machine.

2. Scenario Info

Field Value
Verifies task Export a pricing engine configuration as ORE XML
Parent story Make every configuration screen follow one standard
Target screen Reporting → Product pricing → XVA Overnight, on http://localhost:21002
Clients  
State PASSED

3. Steps

3.1. Log in as the tenant administrator

  • Open http://localhost:21002.
  • Log in as tenant_admin@acme_corporation with Secure-Password-123.
  • Choose the party ACME Corporation HK Ltd.

3.1.1. Result

Field Value
Status PASS

3.2. Open the configuration to export

  • Open Reporting, then Product pricing.
  • Open XVA Overnight.
  • Open the Products tab. The configuration holds five products, named in words.

3.2.1. Result

Field Value
Status PASS

3.3. Read what the Export press will write

  • In the record header, beside Edit, choose Export.
  • A dialog opens and says Writes pricingengine.xml with 5 products.
  • The dialog states that the server writes the file and the browser saves it.

3.3.1. Result

Field Value
Status PASS

3.4. Save the file the server names

  • Press Export in the dialog.
  • The browser saves a file named pricingengine.xml; the name comes from the response, not from the dialog.
  • No XML is shown in a text field and the page does not parse it.

3.4.1. Result

Field Value
Status PASS

3.5. Read the file as ORE reads it

  • Run xmllint --noout pricingengine.xml. It reports no error.
  • The root element is PricingEngines.
  • It holds five Product elements, in this order: Swap, CrossCurrencySwap, FxForward, CreditDefaultSwap, Bond.
  • Each product states a Model, a ModelParameters, an Engine and an EngineParameters.
  • GlobalParameters follows the products and holds ContinueOnCalibrationError true.
  • The engine parameters carry ORE's own names, such as Training.Sequence.

3.5.1. Result

Field Value
Status PASS

3.6. Get the same bytes from the shell

  • In the shell, pricing_engines export <configuration id> --file from_shell.xml, with the id the record page shows.
  • The command reports the file it wrote as pricingengine.xml.
  • cmp from_shell.xml pricingengine.xml reports no difference.

3.6.1. Result

Field Value
Status PASS

4. Results

Field Value
Status PASSED
Completed at 2026-10-27T19:08:42Z
Branch  
Commit  
Worktree  

5. Notes

  • The name comes from ores_reporting_file_types_tbl: the row for pricing_engines whose kind is input_document and whose direction is input, with is_default winning when a kind has several. A table with no such row refuses the export rather than inventing a name.
  • The dialog's sentence uses a constant for the name today, so a tenant that renames the row would see the old name before the press while the saved file still takes the server's name. That is the one known gap; the test checks the saved file, not the pre-press sentence.

Emacs 29.3 (Org mode 9.6.15)