View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005365 | Taler | merchant backend | public | 2018-06-26 13:13 | 2019-12-20 18:12 |
| Reporter | Marcello Stanisci | Assigned To | Marcello Stanisci | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 0.6 | Fixed in Version | 0.6 | ||
| Summary | 0005365: Caching results makes testing difficult. | ||||
| Description | Both /track/transaction and /track/transfer from the merchant use to cache the response from the exchange. Although this helps for performance, this makes harder to get those two API endpoint Twister-tested. So this issue claims that a new utility/technique should be developed so that Twister-testing /track/transaction and /track/transfer becomes easier and faster. | ||||
| Tags | No tags attached. | ||||
| related to | 0005366 | closed | Marcello Stanisci | Need payment generator for corner cases. |
| child of | 0004930 | closed | Marcello Stanisci | Render 'conflict' errors due to /track operations. |
| There is no way to interfere with how caching is carried out. In other words, there is no way to not use cached results to track order_id x on the second request of /track/transaction for x. However, more and more x-like orders can be created, so that the tester does not run out of trackable orders "soon". | |
| 0d2b620 implements "rewinding" of CMDs for the "alt" payment generator. The ordinary payment generator had already this feature. The issue stays open to remind that manual tests via the back-office site have to be done. | |
| Manual test passed. Give the following command to generate 'n' payment entries, each of which gets its individual wire transfer. $ taler-merchant-generate-payments-alt -m http://merchant -b http://bank -i X -t 'n' | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2018-06-26 13:13 | Marcello Stanisci | New Issue | |
| 2018-06-26 13:13 | Marcello Stanisci | Status | new => assigned |
| 2018-06-26 13:13 | Marcello Stanisci | Assigned To | => Marcello Stanisci |
| 2018-06-26 13:26 | Marcello Stanisci | Relationship added | child of 0004930 |
| 2018-06-26 13:27 | Marcello Stanisci | Relationship added | related to 0005366 |
| 2018-06-26 13:47 | Marcello Stanisci | Note Added: 0013084 | |
| 2018-06-26 13:48 | Marcello Stanisci | Note Edited: 0013084 | |
| 2018-06-28 19:45 | Marcello Stanisci | Note Added: 0013108 | |
| 2018-06-29 07:42 | Marcello Stanisci | Note Added: 0013112 | |
| 2018-06-29 07:42 | Marcello Stanisci | Status | assigned => informing |
| 2018-06-29 07:42 | Marcello Stanisci | Resolution | open => fixed |
| 2018-07-02 08:27 | Christian Grothoff | Product Version | => git (master) |
| 2018-07-02 08:27 | Christian Grothoff | Fixed in Version | => 0.6 |
| 2019-12-20 18:12 | Christian Grothoff | Status | informing => closed |
| 2025-03-22 13:09 | Christian Grothoff | Category | mechant backend => merchant backend |