View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003475 | Taler | exchange | public | 2014-07-01 16:47 | 2019-12-20 18:12 |
| Reporter | Florian Dold | 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 | low | Severity | feature | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 0.6 | Fixed in Version | 0.6 | ||
| Summary | 0003475: evil customer testsuite | ||||
| Description | There should be an "evil" customer testsuite, which tries to trigger edge- or error cases in the exchange implementation. | ||||
| Tags | No tags attached. | ||||
| I think the existing Twister tests do some (or most) of this already, we should check code coverage to find out what is missing. | |
| Yes, I'm just not super happy with the fact that the coverage we trust is done over the *exchange-lib* instead of the exchange httpd itself. | |
| Indeed, that's not a good way to do the coverage. But is that a fundamental problem? Could we not adjust the scripts to get code coverage over both the exchange-lib and the exchange? Running 'lcov' top-level should to the trick, or not? | |
| I just looked over the code coverage reports, and I think we can consider this one resolved (for the exchange). | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2014-07-01 16:47 | Florian Dold | New Issue | |
| 2014-07-01 16:47 | Florian Dold | Status | new => assigned |
| 2014-07-01 16:47 | Florian Dold | Assigned To | => user773 |
| 2015-01-29 15:34 | Christian Grothoff | Severity | minor => feature |
| 2015-03-22 13:32 | Christian Grothoff | Priority | normal => low |
| 2015-03-22 13:33 | Christian Grothoff | Assigned To | user773 => |
| 2015-03-22 13:33 | Christian Grothoff | Status | assigned => implementing |
| 2015-04-13 01:14 | Christian Grothoff | Product Version | => git (master) |
| 2015-04-13 01:14 | Christian Grothoff | Target Version | => 0.6 |
| 2016-02-18 14:43 | Christian Grothoff | Category | mint => exchange |
| 2016-03-20 20:53 | Torsten Grothoff | Issue cloned: 0004328 | |
| 2016-05-04 04:50 | Christian Grothoff | Description Updated | |
| 2016-05-04 04:51 | Christian Grothoff | Relationship added | child of 0004454 |
| 2018-03-27 15:31 | Christian Grothoff | Note Added: 0012907 | |
| 2018-03-27 15:31 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2018-03-27 15:31 | Christian Grothoff | Status | implementing => assigned |
| 2018-03-27 15:32 | Christian Grothoff | Relationship deleted | child of 0004454 |
| 2018-06-12 07:02 | Christian Grothoff | Assigned To | Christian Grothoff => Marcello Stanisci |
| 2018-06-12 09:03 | Marcello Stanisci | Note Added: 0013035 | |
| 2018-09-14 21:26 | Christian Grothoff | Note Added: 0013230 | |
| 2018-09-17 09:30 | Christian Grothoff | Status | assigned => informing |
| 2018-09-17 09:30 | Christian Grothoff | Resolution | open => fixed |
| 2018-09-17 09:30 | Christian Grothoff | Fixed in Version | => 0.6 |
| 2018-09-17 09:30 | Christian Grothoff | Note Added: 0013232 | |
| 2019-12-20 18:12 | Christian Grothoff | Status | informing => closed |