Test Hooks for the Center

[BillHodghead]

From @bhcrosslake on June 21, 2017 0:49

In order to do use case and service integration testing we need to be able to configure the service and cause failures at the appropriate times.

• Reject Transfers Be able to programmatically reject a transfer from the center (I think this is already possible with the existing API, but I'm unclear on whether that can be initiated by the center)

• Cut connections

  • Cut fulfillment notification messages for center
  • Be able to re-establish the connection before or after the payment timeout

• Stop Services

  • Take down central ledger
    • After receiving prepare and before sending notification
      • Bring up while payment is valid
      • Bring up after payment has timed out
    • After receiving fulfill and before sending notification
      • Bring up while payment is valid
      • Bring up after payment has timed out

• Configure route fees

• View transfer record and status for a given transfer including fees there is an API for this, but it doesn't appear to separate the fees such as the route fee

Copied from original issue: LevelOneProject/Docs#540

[BillHodghead]

From @adamsteenhard on August 28, 2017 13:38

@bhcrosslake I do not recall discussing this story as part of the PI - 7.0 commitments.

[BillHodghead]

My mistake, moving to phase II.