Improve test suites to detect changes in how ynabber works #116
Description
There have been changes which, while improving usage for some users, at the same time break ynabber for others.
Sometimes breaking changes are needed but now they seem to happen without nobody noticing immediately.
Although this is hard to define, it would be an improvement to enhance testing so that the behavior of existing features does not change or, if it does, this will be documented. This could be accomplished by more thorough automated tests.
Since version 0.7 at least the following items are making current versions as yet unusable for me:
- ynabber no longer adequately exits with an error
- (current main) memo field is no longer copied from remittanceInformationUnstructured (appears to be under debate but the old operation is definitely desirable for me)
- (now fixed) having an interval of zero did not cause ynabber to exit after one interation
- bumping into rate limit is not an error
Some of these are already open as issues but it would be an improvement to have more tests for existing usage. However, it is counterproductive to introduce these by accident when they could be easily prevented by more thorough automated tests.
In the past, this has happened on other features. And I may be introducing something that is an issue for others. How can we improve the testing suite so that existing usage does not change without developer noticing it? Perhaps AI could help here?