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
Currently the E2E tests start the OpenMeter services (api, sink-worker) as dagger services which has the limitation that the service logs from the test runs are not easily accessible (see links).
While it is true that the responses returned from the services are sufficient for the assertions made in the tests, actually writing or debugging the tests is significantly harder without access to the logs, which can have the negative effect of encouraging less optimal testing approaches.
The simplest solution might be to do away with dagger for the E2E service orchestration until this functionality is supported.
Currently the E2E tests start the OpenMeter services (api, sink-worker) as dagger services which has the limitation that the service logs from the test runs are not easily accessible (see links).
While it is true that the responses returned from the services are sufficient for the assertions made in the tests, actually writing or debugging the tests is significantly harder without access to the logs, which can have the negative effect of encouraging less optimal testing approaches.
The simplest solution might be to do away with dagger for the E2E service orchestration until this functionality is supported.
Dagger Issues relating to accessing Service logs:
dagger/dagger#6965
dagger/dagger#7377
The text was updated successfully, but these errors were encountered: