arkmq-org/arkmq-org-broker-operator

investigate and rationalise our tests, ginkgo vs go test

Open

#1,375 opened on Apr 9, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (70 forks)auto 404
enhancementgohelp wanted

Repository metrics

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

Description

in debugging in particular, a ginkgo test run will pick up the go tests, your break point can be hit many times before matching the scenario being investigated.

it seems we should just use ginkgo everywhere. maybe we should research what others do, but whatever is simplest we should do to make debugging easier.

it may just be more packages are necessary.

Contributor guide

Research direction
Research how other Go projects handle ginkgo vs go test integration, and propose a simple solution to use ginkgo everywhere.
Tech stack
go
Domain
testingbackend
Issue type
Research
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
GoGinkgotesting
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70