Retail order system / employees-add-delete

employees-add-delete

Add a record, save, delete the unreferenced fixture record.

0defects

78values match

4tolerated by policy

0waived

12unmapped

Unmapped values are recorded on the original but have no counterpart the mapping names in the migrated app, so they are listed, not compared, and are not defects. Here: the Forms record indicator ("Record: 1/2" in the status bar) (6); the list of open Forms windows (6).

Three runs from a fresh database gave byte-identical diffs. Behaviour that looks odd in the migrated app but is the original's: faithful to the original and waivers. Files: scenario, golden record, target record, diff (JSON).

Scenario steps

Items are addressed by their Forms name (BLOCK.ITEM[row]), the same name in the original and, through the mapping, in the migrated app.

#	Step	Action	Checked on the original
0		Open form `employees_form`
1	add new	Click `EMPLOYEES.ADD_BTN`
2	fields	Type `EMPLOYEES.EMPLOYEE_ID` = 903, `EMPLOYEES.NAME` = New Waiter, `EMPLOYEES.PHONE` = 0100000905, `EMPLOYEES.ROLE` = Waiter, `EMPLOYEES.SALARY` = 4000
3	save	Click `EMPLOYEES.SAVE_BTN`
4	last record	Click `EMPLOYEES.ITEM16`	`EMPLOYEES.NAME[0]` = Fixture Cashier
5	delete	Click `EMPLOYEES.DELETE_BTN`

Screens, step by step

Left: the original Oracle Forms application, recorded on a virtual display. Right: the migrated application in headless Chromium. Screenshots are evidence only; the comparison works on the recorded values.

Step 0: open employees_form

Original (Oracle Forms 14.1.2), step 00-open — Original (Oracle Forms 14.1.2)

Migrated (.NET, PostgreSQL), step 00-open — Migrated (.NET, PostgreSQL)

Step 1: add new

Original (Oracle Forms 14.1.2), step 01-add-new — Original (Oracle Forms 14.1.2)

Migrated (.NET, PostgreSQL), step 01-add-new — Migrated (.NET, PostgreSQL)

Step 2: fields

Original (Oracle Forms 14.1.2), step 02-fields — Original (Oracle Forms 14.1.2)

Migrated (.NET, PostgreSQL), step 02-fields — Migrated (.NET, PostgreSQL)

Step 3: save

Original (Oracle Forms 14.1.2), step 03-save — Original (Oracle Forms 14.1.2)

Migrated (.NET, PostgreSQL), step 03-save — Migrated (.NET, PostgreSQL)

Step 4: last record

Original (Oracle Forms 14.1.2), step 04-last-record — Original (Oracle Forms 14.1.2)

Migrated (.NET, PostgreSQL), step 04-last-record — Migrated (.NET, PostgreSQL)

Step 5: delete

Original (Oracle Forms 14.1.2), step 05-delete — Original (Oracle Forms 14.1.2)

Migrated (.NET, PostgreSQL), step 05-delete — Migrated (.NET, PostgreSQL)

Golden record of the original

After each step: the focus, the displayed values that changed, the message line and any alert. The full record (every item of every step, windows, lists of values) is in the JSON file.

#	Step	Action (by name)	Focus after	Displayed values that changed	Message line	Expect
0		`Open form employees_form`	`EMPLOYEES.EMPLOYEE_ID[0]`	`EMPLOYEES.EMPLOYEE_ID[0]` = 1 `EMPLOYEES.NAME[0]` = Ammar `EMPLOYEES.PHONE[0]` = 01012345678 `EMPLOYEES.ROLE[0]` = Manager `EMPLOYEES.SALARY[0]` = 15000
1	add new	`Click EMPLOYEES.ADD_BTN`	`EMPLOYEES.EMPLOYEE_ID[0]`
2	fields	`Type EMPLOYEES.EMPLOYEE_ID = 903, EMPLOYEES.NAME = New Waiter, EMPLOYEES.PHONE = 0100000905, EMPLOYEES.ROLE = Waiter, EMPLOYEES.SALARY = 4000`	`EMPLOYEES.SALARY[0]`	`EMPLOYEES.EMPLOYEE_ID[0]` = 903 `EMPLOYEES.NAME[0]` = New Waiter `EMPLOYEES.PHONE[0]` = 0100000905 `EMPLOYEES.ROLE[0]` = Waiter `EMPLOYEES.SALARY[0]` = 4000
3	save	`Click EMPLOYEES.SAVE_BTN`	`EMPLOYEES.SAVE_BTN[0]`		FRM-40400: Transaction complete: 1 records applied and saved.
4	last record	`Click EMPLOYEES.ITEM16`	`EMPLOYEES.EMPLOYEE_ID[0]`	`EMPLOYEES.EMPLOYEE_ID[0]` = 902 `EMPLOYEES.NAME[0]` = Fixture Cashier `EMPLOYEES.PHONE[0]` = 0100000903 `EMPLOYEES.ROLE[0]` = Cashier `EMPLOYEES.SALARY[0]` = 5000		pass
5	delete	`Click EMPLOYEES.DELETE_BTN`	`EMPLOYEES.EMPLOYEE_ID[0]`	`EMPLOYEES.EMPLOYEE_ID[0]` = 903 `EMPLOYEES.NAME[0]` = New Waiter `EMPLOYEES.PHONE[0]` = 0100000905 `EMPLOYEES.ROLE[0]` = Waiter `EMPLOYEES.SALARY[0]` = 4000	FRM-40400: Transaction complete: 1 records applied and saved.

Database effects

EMPLOYEES inserted: {"EMPLOYEE_ID": 903, "NAME": "New Waiter", "PHONE": "0100000905", "ROLE": "Waiter", "SALARY": 4000}
EMPLOYEES deleted: {"EMPLOYEE_ID": 902, "NAME": "Fixture Cashier", "PHONE": "0100000903", "ROLE": "Cashier", "SALARY": 5000}

Classified diff against the migrated app

Diff: employees-add-delete
counts: match 78, tolerated 4, waived 0, defect 0, unmapped 12, harness 0
generated-id pairs (source -> target): none

waivers:
  W1 [proposed] ORDER_DATA saved as NULL: applied to 0 value(s)
  W2 [proposed] Order number consumed when the form opens: applied to 0 value(s)
  W3 [proposed] Line ITEM_ID typed by the user: applied to 0 value(s)
  W4 [proposed] Two modal alerts after saving: applied to 0 value(s)
  W5 [proposed] Key debug message on record navigation (single-table forms): applied to 0 value(s)
  W6 [proposed] Customer debug message in ORDERS: applied to 0 value(s)
  W7 [proposed] Placeholder alert on leaving Employees: applied to 0 value(s)
  W8 [proposed] Error message when the application starts: applied to 0 value(s)
  W9 [proposed] Keyboard hint of the Forms client while a question is open: applied to 0 value(s)
  W10 [proposed] An order added with Add cannot be saved: applied to 0 value(s)

[tolerated] db.EMPLOYEES.deleted.SALARY  rule=money  x1
[tolerated] db.EMPLOYEES.inserted.SALARY  rule=money  x1
[tolerated] ui.values.EMPLOYEES.SALARY  rule=money  x2
[unmapped] ui.record  (no target counterpart)  x6
[unmapped] ui.windows  (no target counterpart)  x6

Waivers

No waiver applies to this scenario: every compared value matches or is within the tolerance policy.