Switch tests to ginkgo

It's easier to test CLIs with ginkgo and it makes it
easy to assert on the output, rather than metrics. Validating
metrics is tricky, because tests are run concurrently

.github/workflows/ci.yaml

@@ -6,8 +6,8 @@ env:
   TEST_STATS_DELAY: 5000
 
 jobs:
-  golangci:
-    name: lint
+  lint:
+    name: Lint
     runs-on: ubuntu-latest
 
     steps:
@@ -49,4 +49,4 @@ jobs:
         run: OMQ_RABBITMQCTL=DOCKER:${{job.services.rabbitmq.id}} bin/ci/before_build.sh
 
       - name: Run go test
-        run: go test -count=1 -p 1 -v ./...
+        run: go run github.com/onsi/ginkgo/v2/ginkgo -r --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --race --trace

cmd/cmd_suite_test.go

@@ -0,0 +1,13 @@
+package cmd_test
+
+import (
+	"testing"
+
+	. "github.com/onsi/ginkgo/v2"
+	. "github.com/onsi/gomega"
+)
+
+func TestCmd(t *testing.T) {
+	RegisterFailHandler(Fail)
+	RunSpecs(t, "CMD Suite")
+}