Assert service compliance #160
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: This intentionally includes tests that currently fail.Service Compliance information moved to wiki page.
The general point of this PR is to add tests to make sure that all services comply with the first Service Compliance rule:
Added test resulted in the following services that did not pass:
Telegram
Supports Params? ✔ Yes!
Supports Title prop? ⚫ No
Silently ignores title? ❌ Error:
title is not a valid config key [channels notification parsemode preview]
IFTT
Supports Params? ✔ Yes!
Uses title prop? ⚫ No
Silently ignores title? ❌Error
"title is not a valid config key [events messagevalue value1 value2 value3]"
OpsGenie
Supports Params? ✔ Yes!
Uses title prop? ⚫ No
Silently ignores title? ❌ Error:
title is not a valid config key [actions alias description details entity note priority responders source tags user visibleto]
Fixes for the above services were added, and all three now pass. IFTT and OpsGenie can actually make use of the title as well if configured, but Telegram just ignores it.