-
Notifications
You must be signed in to change notification settings - Fork 137
Closed
Labels
refinedRequirements are refined and the issue is ready to be implemented.Requirements are refined and the issue is ready to be implemented.size/mediumEstimated to be completed within a weekEstimated to be completed within a weektestsPull requests that update testsPull requests that update tests
Milestone
Description
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
Acceptance
- Any circumstance where functional tests are sending traffic through a test environment, retries are added.
- Readiness probes are added to all backend manifests.
Metadata
Metadata
Assignees
Labels
refinedRequirements are refined and the issue is ready to be implemented.Requirements are refined and the issue is ready to be implemented.size/mediumEstimated to be completed within a weekEstimated to be completed within a weektestsPull requests that update testsPull requests that update tests
Type
Projects
Status
✅ Done