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
As a maintainer of NGF
I want to add retries in NGF functional tests when testing
So that if not all components of the test have been brought up yet, the test does not result in a failure.
Will run 1 of 10 specs
SSSS
------------------------------
• [FAILED] [0.573 seconds]
Basic test example [It] sends traffic [functional]
/Users/luca/src/github.com/lucacome/nginx-kubernetes-gateway/tests/suite/sample_test.go:40
[FAILED] Expected
<int>: 502
to equal
<int>: 200
In [It] at: /Users/luca/src/github.com/lucacome/nginx-kubernetes-gateway/tests/suite/sample_test.go:47 @ 04/18/24 09:21:07.264
------------------------------
SSSSS
Summarizing 1 Failure:
[FAIL] Basic test example [It] sends traffic [functional]
/Users/luca/src/github.com/lucacome/nginx-kubernetes-gateway/tests/suite/sample_test.go:47
Ran 1 of 10 Specs in 15.564 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 9 Skipped
--- FAIL: TestNGF (15.57s)
FAIL
FAIL github.com/nginxinc/nginx-gateway-fabric/tests/suite 16.087s
FAIL
make: *** [test] Error 1
We should:
Add retries
We can also add readiness probes to all our backend manifests.
The text was updated successfully, but these errors were encountered:
As a maintainer of NGF
I want to add retries in NGF functional tests when testing
So that if not all components of the test have been brought up yet, the test does not result in a failure.
We should:
The text was updated successfully, but these errors were encountered: