knative/eventing

Subscription Conformance Tests completion

Open

#5,782 opened on Oct 4, 2021

View on GitHub
 (15 comments) (0 reactions) (1 assignee)Go (632 forks)auto 404
help wantedkind/feature-requesttriage/accepted

Repository metrics

Stars
 (1,551 stars)
PR merge metrics
 (PR metrics pending)

Description

Problem We don't have all the MUST clauses in the Subscription spec covered by tests in the project, for example: https://github.com/knative/eventing/blob/792f56ddb5e2328005149e7af571be6ca667cd89/test/rekt/features/channel/data_plane.go lots of todo in .must clauses in this file. Same with the other CRDs (Subscription, Broker, Trigger)

Persona: Developers

Exit Criteria Have at least one test per MUST clause from the Subscription specs

Additional context (optional) This is part of the Conformance GA plan

Contributor guide

Research direction
Review the existing conformance tests in test/rekt/features/channel/data plane.go and other CRD test files to identify todos and missing MUST clauses from the Subscription spec. Then write test cases for each uncovered MUST clause.
Tech stack
go
Domain
backendcloud
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 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
GoKubernetesKnative EventingTesting
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55