test: added new e2e test to verify that a client, having issued a monitor command, receives all pending notifications
~immediately. This also demonstrates that the socket handling on the server is working properly for multiple writes
in rapid succession. The new test is in tests/at_end2end_test/test/notify_verb_test.dart and is called "monitor receives multiple pending notifications immediately"
build: updated version to 3.0.43
- How I did it
Find all usages of AtConnection.write, ensure those calls are awaited
Modify signatures of calling functions to mark them as async
Modify code which calls those calling functions and await those calls
- How to verify it
Tests pass
Note (1) : New end-to-end test will only work where the 'second' server is running this version or later, as demonstrated by this test run where it succeeds when the 'second' server is cicd2 / cicd6 (which run trunk) but fails when the 'second' server is cicd4 (which runs prod)
Note (2) : New test now does an atServer version check and will run it only when the atServer for the monitor is running 3.0.43 or higher
Note (3) : If you are looking at test logs, the new test is named monitor receives multiple pending notifications immediately
- What I did
tests/at_end2end_test/test/notify_verb_test.dart
and is called "monitor receives multiple pending notifications immediately"- How I did it
AtConnection.write
, ensure those calls areawait
edawait
those calls- How to verify it
monitor receives multiple pending notifications immediately