kubernetes-sigs/cluster-api-provider-aws

Improve testcase naming convention

Open

#3,198 opened on Feb 11, 2022

View on GitHub
 (27 comments) (0 reactions) (2 assignees)Go (689 forks)auto 404
area/testinggood first issuehelp wantedneeds-triagepriority/backlog

Repository metrics

Stars
 (723 stars)
PR merge metrics
 (PR metrics pending)

Description

/area testing

We have started following test naming convention for new test cases in CAPA, we can also do this for existing test cases to bring consistency.

We use this blog for reference. Sample PRs: https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/3160 https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/3091

/good-first-issue

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.