From 31d35d2f77b8ef3c352bb58fac0719c4d61c1c1e Mon Sep 17 00:00:00 2001
From: Radoslav Dimitrov <radoslav@stacklok.com>
Date: Tue, 28 Oct 2025 14:58:53 +0200
Subject: [PATCH] Remove the test-unit-verbose target (#716)

<!-- Provide a brief summary of your changes -->

## Motivation and Context
<!-- Why is this change needed? What problem does it solve? -->
As per @domdomegg's comment -
https://github.com/modelcontextprotocol/registry/pull/713#discussion_r2466295123
## How Has This Been Tested?
<!-- Have you tested this in a real application? Which scenarios were
tested? -->

## Breaking Changes
<!-- Will users need to update their code or configurations? -->

## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update

## Checklist
<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->
- [ ] I have read the [MCP
Documentation](https://modelcontextprotocol.io)
- [ ] My code follows the repository's style guidelines
- [ ] New and existing tests pass locally
- [ ] I have added appropriate error handling
- [ ] I have added or updated documentation as needed

## Additional context
<!-- Add any other context, implementation notes, or design decisions
-->

Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
---
 Makefile | 15 +--------------
 1 file changed, 1 insertion(+), 14 deletions(-)

diff --git a/Makefile b/Makefile
index e3d6fc8..6525459 100644
--- a/Makefile
+++ b/Makefile
@@ -1,4 +1,4 @@
-.PHONY: help build test test-unit test-unit-verbose test-integration test-endpoints test-publish test-all lint lint-fix validate validate-schemas validate-examples check dev-compose clean publisher generate-schema check-schema
+.PHONY: help build test test-unit test-integration test-endpoints test-publish test-all lint lint-fix validate validate-schemas validate-examples check dev-compose clean publisher generate-schema check-schema
 
 # Default target
 help: ## Show this help message
@@ -46,19 +46,6 @@ test-unit: ## Run unit tests with coverage (requires PostgreSQL)
 	@docker compose down postgres >/dev/null 2>&1
 	@echo "✅ Tests complete"
 
-test-unit-verbose: ## Run unit tests with verbose output
-	@echo "Starting PostgreSQL for unit tests..."
-	@docker compose up -d postgres 2>&1 | grep -v "Pulling\|Pulled\|Creating\|Created\|Starting\|Started" || true
-	@echo "Waiting for PostgreSQL to be ready..."
-	@sleep 3
-	@echo ""
-	@echo "Running unit tests (verbose)..."
-	@go test -v -race -coverprofile=coverage.out -covermode=atomic ./internal/... ./cmd/... 2>&1 | grep -v "ld: warning:" | grep -v "^ld:"
-	@echo ""
-	@go tool cover -html=coverage.out -o coverage.html
-	@echo "✅ Coverage report: coverage.html"
-	@docker compose down postgres >/dev/null 2>&1
-
 test: ## Run unit tests (use 'make test-all' to run all tests)
 	@echo "⚠️  Running unit tests only. Use 'make test-all' to run both unit and integration tests."
 	@$(MAKE) test-unit