higress-group/higress

e2e: add testcases for the ext-auth wasmplugin

Open

#1,799 opened on Feb 22, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (1,219 forks)github user discovery
area/e2ehelp wantedsig/wasm

Repository metrics

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

Description

Why do you need it?

Currently, as the functionality of ext-auth is becoming increasingly complex and there are quite a number of users, it would be ideal to introduce e2e testing to assist with regression and testing.

How could it be?

There are a relatively large number of test cases in this area. You can refer to the historical code changes, which generally include combinations of the following scenarios:

  • Using the two endpoint_modes of envoy and forward_auth.
  • Successful authentication and failed authentication.
  • Blacklist and whitelist configurations.

Other related information

https://github.com/alibaba/higress/tree/main/plugins/wasm-go/extensions/ext-auth

Contributor guide

Research direction
Refer to historical code changes in the ext auth plugin directory to understand test patterns. Focus on combinations of endpoint modes (envoy and forward auth), authentication success/failure, and blacklist/whitelist. Then write e2e tests to cover these scenarios.
Tech stack
gowasm
Domain
backendapi
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.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60