2018-05-25
This commit is contained in:
parent
93b4ca8820
commit
eb8893cb21
16
log.md
16
log.md
@ -286,4 +286,18 @@ Started BRIDGE-1163 - Add description to rule
|
||||
|
||||
*DONE* BRIDGE-1162 - metaData appears to be RulesTriggerData
|
||||
|
||||
*DONE* BRIDGE-1163 - Add description to rule
|
||||
*DONE* BRIDGE-1163 - Add description to rule
|
||||
|
||||
##### 2018-05-23 // Wednesday #####
|
||||
|
||||
*DONE* BRIDGE-1165 - Wiki not updated
|
||||
|
||||
Started BRIDGE-906 Request Id should implemented in the Activity Log
|
||||
|
||||
##### 2018-05-24 // Thursday #####
|
||||
|
||||
*DONE* BRIDGE-906 Request Id should implemented in the Activity Log
|
||||
|
||||
##### 2018-05-25 // Friday #####
|
||||
|
||||
|
||||
|
1
tasks/bridge-1163/wiki
Normal file
1
tasks/bridge-1163/wiki
Normal file
@ -0,0 +1 @@
|
||||
┗ OrderDescription STRING Freeform description of the order, as will appear on receipts etc. Create Update 7.2
|
56
tasks/bridge-906/commit.md
Normal file
56
tasks/bridge-906/commit.md
Normal file
@ -0,0 +1,56 @@
|
||||
BRIDGE-906 Request Id should implemented in the Activity Log
|
||||
|
||||
# Summary
|
||||
|
||||
* The Morgan string was extended to include the BridgeUniqueId if available
|
||||
* When the log is written to the database, the BridgeUniqueId is extraxted as reqID
|
||||
* The string is reconstituded without the BridgeUniqueId at the end so as not to interfere with log readers
|
||||
* The reqId is added to ActivityLog
|
||||
* Morgan-mongo-spec.js was updated to test the new reqID
|
||||
|
||||
# Test Plan
|
||||
|
||||
* Run All tests
|
||||
* Run Morgan mongo stream
|
||||
|
||||
```
|
||||
Morgan mongo stream PASSED
|
||||
With an online database PASSED
|
||||
✓ Test logs the record to stdout PASSED
|
||||
✓ Test writes stream records to the database PASSED
|
||||
✓ Test adds timestamp to the record stored in the database PASSED
|
||||
|
||||
With an offline database PASSED
|
||||
That stays offline for 1000 records PASSED
|
||||
Then recovers PASSED
|
||||
✓ Test logs the record to stdout PASSED
|
||||
✓ Test writes all records (including ones cached when offline) to the database PASSED
|
||||
|
||||
Then receives a 1001st record with offline db PASSED
|
||||
Then recovers PASSED
|
||||
✓ Test logs the record to stdout PASSED
|
||||
✓ Test writes all cached records and the new record, but not the 1001st one, to the database PASSED
|
||||
✓ Test still logs the incoming record to stdout PASSED
|
||||
✓ Test reports a data loss warning on stderr PASSED
|
||||
✓ Test still logs the incoming records to stdout PASSED
|
||||
✓ Test doesn't report any errors PASSED
|
||||
✓ Test logs the record to stdout PASSED
|
||||
✓ Test does not attempt to stream records to the database PASSED
|
||||
|
||||
With a pending database write PASSED
|
||||
With another write after the pending one resolves successfully PASSED
|
||||
✓ Test logs the one buffered during the pending, and the new one PASSED
|
||||
|
||||
With another write after the pending one resolves unsuccessfully PASSED
|
||||
✓ Test logs the pending record that failed + the one bufferd during pending, and the new one PASSED
|
||||
✓ Test logs the pending and subsequent record to stdout PASSED
|
||||
✓ Test does not attempt to stream the subsequent record to the database PASSED
|
||||
|
||||
It can process the requestId correctly PASSED
|
||||
✓ Test logs the record to stdout PASSED
|
||||
✓ Test writes stream records to the database PASSED
|
||||
✓ Test adds timestamp to the record stored in the database PASSED
|
||||
✓ Test is an object-mode stream PASSED
|
||||
21 Of 21 Passing
|
||||
|
||||
```
|
Loading…
Reference in New Issue
Block a user