TestSuite extension mechanism #146
Conversation
…Parser read in inherited fields as well
|
Perhaps a changelog entry and/or a short explanation in the readme for the extension mechanism would be useful. |
I had thought about that and I even started writing one, but when reading through those files, I realised that they are more descriptions for the users of the resulting executable than they are descriptions for the developers. Thus I think this kind of change should not be written down there for consistency. |
You're probably right, it's fine for me. |
Make it easier to extend TestSuite with test cases and let TomlConfigParser read in inherited fields as well. # Checklist The following aspects have been respected by the author of this pull request, confirmed by both pull request assignee **and** reviewer: * Adherence to coding conventions * [x] @maximilianpilz * [x] @belagertem * Adherence to javadoc conventions * [x] @maximilianpilz * [x] @belagertem * Changelog update (necessity checked and entry added or not added respectively) * [x] @maximilianpilz * [x] @belagertem * README update (necessity checked and entry added or not added respectively) * [x] @maximilianpilz * [x] @belagertem * config update (necessity checked and entry added or not added respectively) * [x] @maximilianpilz * [x] @belagertem * SDCcc executable ran against a test device (if necessary) * [x] @maximilianpilz * [x] @belagertem
Make it easier to extend TestSuite with test cases and let TomlConfigParser read in inherited fields as well.
Checklist
The following aspects have been respected by the author of this pull request, confirmed by both pull request assignee and reviewer: