search

kubewarden / kubewarden-end-to-end-tests

Files used to run Kubewarden end-to-end tests
https://kubewarden.io
Apache License 2.0
2 stars 6 forks source link

e2e Feature Request: add timestamp #104

Closed flavio closed 3 months ago

flavio commented 3 months ago

Is your feature request related to a problem?

I was looking into an e2e tests failure log, trying to understand if I was running into a timeout issue.

Unfortunately all the output produced by the e2e tests doesn't have a timestamp associated. That makes impossible to understand how much time passed between two log statements.

Solution you'd like

All the output of the e2e tests should have a timestamp: date and time

Alternatives you've considered

No response

Anything else?

No response

fabriziosestito commented 3 months ago

Maybe this is a noop, see https://github.com/debug-js/debug/issues/565#issuecomment-1335344834

image

flavio commented 3 months ago

Thanks for the tip, we can close this issue if you want @kravciak

kravciak commented 3 months ago

I found -T Add timing information to tests bats option. I will test what it does (to have something on local runs too).

kravciak commented 3 months ago

I created https://github.com/kubewarden/kubewarden-end-to-end-tests/pull/105. Timing information in bats are quite limited, github action timestamps are much better.

For example here only adds 43214 - test duration in milliseconds..

monitor-mode-tests.bats
 ✓ [Monitor mode end-to-end tests] Install ClusterAdmissionPolicy in monitor mode [43214 (timeout: 5m)]
   clusteradmissionpolicy.policies.kubewarden.io/privileged-pods created
   clusteradmissionpolicy.policies.kubewarden.io/privileged-pods condition met
   deployment "policy-server-default" successfully rolled out
   clusteradmissionpolicy.policies.kubewarden.io/privileged-pods condition met