v2.0.0

[2.0.0] - 2022-01-05

This new major version release is due to a non-backward-compatible change in the test service protocol (regarding the listen command). Be aware that projects that currently pass the tests might fail in the future due to a new mandatory test in a minor version release, if the new test is for behavior that was already required by the specification. See docs/deploying.md for more about versioning of this tool.

Added:

• New mandatory test: the client must automatically follow an HTTP 301 or 307 redirect.
• New mandatory test: the client must ignore any id field whose value contains a null.
• New mandatory test: the client must allow the last event ID to be overwritten with an empty value if an event explicitly provides an id field with an empty value.
• New mandatory test: any non-empty line that does not contain a colon must be treated as a field with an empty value (e.g., data should be treated the same as data:).
• New mandatory test: the client must not retain any part of a partly-parsed but incomplete message if the connection is dropped.

Changed:

• For test service implementations that recognize the listen command, the schema for the request body has been changed.
• The test framework has been rewritten using a somewhat different approach similar to https://github.com/launchdarkly/sdk-test-harness, with a cleaner separation of concerns. This should make the test logic easier to follow.