0005850: revise test cases that check for error messages

ID	Project	Category	View Status	Date Submitted	Last Update

0005850	Taler	obsolete component	public	2019-08-23 16:12	2021-08-24 16:23

Reporter	Florian Dold	Assigned To	MS
Priority	normal	Severity	tweak	Reproducibility	have not tried
Status	closed	Resolution	won't fix
Target Version	0.8	Fixed in Version	0.8

Summary	0005850: revise test cases that check for error messages
Description	Some test cases currently check that some error will occur. It does this by running the test suite with a modified config, and then checks if the test runner returns a non-zero result. This results in really confusing logs. We should have separate unit tests to check if wrong or missing config values are handled incorrectly. However, these shouldn't result into output where the test runner (!!) says that there was an error, but then the test case succeeds. I've disabled these tests for now.
Tags	No tags attached.

Date Modified	Username	Field	Change
2019-08-23 16:12	Florian Dold	New Issue
2019-08-23 16:12	Florian Dold	Status	new => assigned
2019-08-23 16:12	Florian Dold	Assigned To	=> Marcello Stanisci
2020-09-04 14:40	MS	Assigned To	Marcello Stanisci => MS
2020-09-05 13:53	Christian Grothoff	Severity	minor => tweak
2020-09-11 15:02	MS	Status	assigned => resolved
2020-09-11 15:02	MS	Resolution	open => won't fix
2020-09-11 15:02	MS	Note Added: 0016964
2020-10-03 14:08	Christian Grothoff	Fixed in Version	=> 0.8
2020-10-03 14:10	Christian Grothoff	Target Version	=> 0.8
2021-08-24 16:23	Christian Grothoff	Status	resolved => closed
2022-08-23 20:26	Christian Grothoff	Category	bank (demonstrator) => py bank (demonstrator, obsolete)
2023-12-03 01:23	Christian Grothoff	Category	py bank (demonstrator, obsolete) => obsolete componet
2023-12-11 20:08	Florian Dold	Category	obsolete componet => obsolete component

MS 2020-09-11 15:02 reporter ~0016964	This is overkill for the Python bank. We don't have such tests not even for components like the exchange, for example.