meshery / meshery/meshkit

[CI] Methodology to test MeshKit builds

Open
#434 14 comments 0 reactions 0 assignees View on GitHub
area/ci help wanted issue/willfix kind/enhancement language/go
Dominant language
Go
Stars
223
Forks
225
Avg merge
7d 1h
Merged PRs (30d)
1

Description

**Current Behavior**
When Dependabot stops by and suggests an upgraded dependency, we don't know if that dependency upgrade is compatible given a lack of integration test workflows.

**Desired Behavior**
Improved workflow to validate MeshKit functions.

Integration and functional test workflows can be borrowed from meshery/meshery.

---
**Resources**

**Alternatives / Additional Context**

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the integration and functional test workflows in meshery/meshery, then inspect MeshKit's existing build and dependency workflows. Done means the repository has workflows that exercise MeshKit functions and can detect incompatible dependency upgrades.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
ci-cd, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.