Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
code client-side
|
|
failure context
|
|
for a coin we never saw
|
|
|
|
|
|
|
|
|
|
JSON, or 400 the requester; similarly don't tolerate anything else as client
|
|
|
|
batches, modify API to rewind to label
|
|
inside of the testing logic
|
|
|
|
|
|
|
|
reserve_priv doesn't exist
|
|
deep copies
|
|
a struct (simplifies merchant later)
|
|
deep copies
|
|
a struct (simplifies merchant later)
|
|
|
|
|
|
deep copies
|
|
a struct (simplifies merchant later)
|
|
|
|
|
|
|
|
|
|
|
|
deep copies
|
|
a struct (simplifies merchant later)
|
|
TALER_EXCHANGE_transfers_get() -- simplifies merchant later
|
|
|
|
|
|
|
|
|
|
give time to payments to settle, before requesting
/history/incoming and /history/outgoing.
|
|
and fix their deletion before running the test.
|
|
more preparation
|
|
|
|
Prefer the 'iban' method over the 'x-taler-bank',
regarding the payto:// URIs. Tests are still using
the loopback bank connection, though.
|
|
|
|
Up to the point where Nexus gets launched and
the Exchange user & bank connection get created.
The test fails because the bank connection of
type "loopback" is not implemented in the nexus
yet.
|