You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Several integrations that rely on external APIs use stream as their test services to build mocks and run system tests.
There are some blind spots when it comes to detecting config errors that could lead to wrong pagination, infinite pagination loops, etc. mainly caused by the inability of elastic-package to detect anything else than is there any data? in the data stream or is there the expected number of events? if assert.hit_count is set, which makes things better but is not enough.
As part of an effort to improve system tests robustness some things could be improved:
Several integrations that rely on external APIs use
stream
as their test services to build mocks and run system tests.There are some blind spots when it comes to detecting config errors that could lead to wrong pagination, infinite pagination loops, etc. mainly caused by the inability of
elastic-package
to detect anything else thanis there any data?
in the data stream oris there the expected number of events?
ifassert.hit_count
is set, which makes things better but is not enough.As part of an effort to improve system tests robustness some things could be improved:
data_stream/_dev/test/system/config.yml
to fail the tests if the test services exit unsuccessfully. Add ignore_service_error flag to selectively ignore test service errored containers #1540Once this is done we can leverage these new behavior for system tests that require it.
The text was updated successfully, but these errors were encountered: