higress-group/higress

Add e2e test for upstream retry annotations

Open

#172 opened on Feb 6, 2023

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (1,219 forks)github user discovery
area/annotationarea/e2ehelp wantedlevel/challengesig/automation

Repository metrics

Stars
 (9,036 stars)
PR merge metrics
 (Avg merge 7d 9h) (18 merged PRs in 30d)

Description

annotation: nginx.ingress.kubernetes.io/proxy-next-upstream nginx.ingress.kubernetes.io/proxy-next-upstream-timeout nginx.ingress.kubernetes.io/proxy-next-upstream-tries

e2e framework: https://github.com/alibaba/higress/tree/main/test

part of #190

Contributor guide

Research direction
Examine the existing e2e tests in /test for patterns, then create new test cases covering the proxy next upstream annotations outlined in the issue. Ensure tests verify correct upstream retry behavior.
Tech stack
go
Domain
backendtesting
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75