higress-group/higress

e2e: add testcases for auth annotations

Open

#200 opened on Feb 16, 2023

View on GitHub
 (5 comments) (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

Why do you need it?

annotations:

  • nginx.ingress.kubernetes.io/auth-type
  • nginx.ingress.kubernetes.io/auth-secret
  • nginx.ingress.kubernetes.io/auth-secret-type
  • nginx.ingress.kubernetes.io/auth-realm

How could it be?

Add testcases for auth annotations.

Other related information

Contributor guide

Research direction
Examine the existing e2e test structure in the /test directory, understand how tests are written (likely using Ginkgo/Gomega), and add test cases for each of the listed annotations covering both valid and invalid configurations. Refer to issue #190 for context.
Tech stack
go
Domain
backendtestingauthentication
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-2 days
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.
Mostly clear
Prerequisites
GoKubernetestesting
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65