envoyproxy/envoy

tooling: tests for protodoc

Open

#18,271 opened on Sep 27, 2021

View on GitHubContributor guide
 (1 comment) (0 reactions) (1 assignee)C++ (5,373 forks)batch import
area/docshelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (PR metrics pending)

Description

This tool has become quite complex and would benefit from some tests.

Contributor guide

Research direction
Examine the protodoc tool's source code and existing tests to identify key components, then implement unit or integration tests to cover its functionality.
Tech stack
cpp
Domain
testing
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.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++Testing frameworks
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75