Declared behaviors match
0 changed3 matched3 scenarios recorded
Only declared workloads were tested. “Same” compares values and types, not just row counts.
Scroll a comparison to see every column. Keyboard: focus the table and use arrow keys.
Search an updated article
matched| Witness | Before | After migration | Result |
|---|---|---|---|
| Step 1 | ok | ok | same |
| Updated article appears in searchordered comparison | 1 row1 column | 1 row1 column | same |
Search an inserted article
matched| Witness | Before | After migration | Result |
|---|---|---|---|
| Step 1 | ok | ok | same |
| Inserted article appears in searchordered comparison | 1 row1 column | 1 row1 column | same |
Remove a deleted article from search
matched| Witness | Before | After migration | Result |
|---|---|---|---|
| Step 1 | ok | ok | same |
| Deleted article has no search hitordered comparison | 0 rows1 column | 0 rows1 column | same |
Database checks
- BeforeIntegrity passed · foreign keys passed
- AfterIntegrity passed · foreign keys passed
Schema changes
- No schema object differences recorded.
Reproduction evidence
- SQLite engine
- 3.50.4
- Copied snapshot SHA-256
- 9ebcae997f2f83395db5061f067d4da70c349715ca9fbf929b07e51aece0befa
- Migration SHA-256
- 16a3765ccacc2ec453aae6b436c427da3299609c6068466a519f2d88ba41741f
- Suite SHA-256
- a4fc2a9f7819a24d87b635e576565b4c2060fa7f43a6e9f945994fec973746e9
Method, privacy and limits
Each scenario starts with its own fresh copies of the same database snapshot. The same steps run before and after migration. Comparisons preserve value types, values and duplicate rows, using each observation’s declared ordering.
Schema differences provide context. Passing integrity and foreign-key checks does not establish unchanged application behavior.
Only declared scenarios were examined. A match is not a guarantee about other workloads, database versions, production concurrency or malicious input.
This report omits the database snapshot, SQL, bound parameters, source paths, raw result cells and raw SQLite error messages. Scenario, observation and schema names, shapes and hashes remain visible metadata. Retain original input files privately.
No external assets or requests.