KusionStack/kusion

Test: improve test coverage

Open

#991 opened on Apr 1, 2024

View on GitHubContributor guide
 (4 comments) (0 reactions) (1 assignee)Go (108 forks)auto 404
area/testgood first issuehacktoberfesthelp wanted

Repository metrics

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

Description

What would you like to be added?

Improve test coverage to 75+%

Why is this needed?

Test coverage has dropped a lot since the recent upgrade

Contributor guide

Research direction
Identify untested modules by running coverage reports and write tests for uncovered code paths.
Tech stack
go
Domain
backend
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.
Half day
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.
Clear
Prerequisites
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60