knative / knative/eventing

Add the broker classes consideration into the test cases

Open
#7,660 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/test-and-release kind/feature-request triage/accepted
Dominant language
Go
Stars
1.6k
Forks
631
Avg merge
3d 13h
Merged PRs (30d)
6

Description

Problem
Adding more test cases to test out the broker classes configuration in the default broker class configuration.
The tests that get involved are unit tests.

Files involved:
pkg/apis/eventing/v1/broker_defaults_test.go

Persona:
Which persona is this feature for? Contributors

Exit Criteria
A measurable (binary) test that would indicate that the problem has been resolved.

Time Estimate (optional):
How many developer-days do you think this may take to resolve? 1

Additional context (optional)
https://github.com/knative/eventing/pull/7631#discussion_r1481686685

/triage accepted

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the unit tests in pkg/apis/eventing/v1/broker_defaults_test.go and review the broker class configuration discussion linked from pull request 7631. Identify the missing broker class cases for the default broker configuration, add measurable unit-test coverage, and run the relevant tests to confirm they pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, testing
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.