From 0b1c5f90be4b9125f13331e3d5f7fc5b4aa928b7 Mon Sep 17 00:00:00 2001
From: jnasbyupgrade <jnasby@upgrade.com>
Date: Mon, 12 Oct 2026 18:17:03 -0500
Subject: [PATCH] Verify make pgtle produces output for both extensions

The multi-extension test only checked that `make pgtle` exits 0. The
`pgtle` recipe joins its per-extension pgtle.sh calls with `;`, so only
the last extension's status reaches make: a failure (or a skipped
extension) for ext_alpha still exits 0.

Assert that at least one `pg_tle/<range>/` directory exists and that
every range contains both `ext_alpha.sql` and `ext_beta.sql`.

Fixes #71

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
---
 test/standard/multi-extension.bats | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/test/standard/multi-extension.bats b/test/standard/multi-extension.bats
index 656a717..28b1aac 100644
--- a/test/standard/multi-extension.bats
+++ b/test/standard/multi-extension.bats
@@ -118,6 +118,18 @@ setup() {
   # trimming (issues #25, #26).
   run make pgtle
   assert_success
+
+  # make's exit status alone can't prove both extensions were processed: the
+  # pgtle recipe joins its per-extension pgtle.sh calls with ';', so only the
+  # last one's status counts. Check every range has output for both.
+  local ranges=(pg_tle/*/)
+  [ -d "${ranges[0]}" ] || error "make pgtle created no pg_tle/<range>/ directories"
+  local range ext
+  for range in "${ranges[@]}"; do
+    for ext in ext_alpha ext_beta; do
+      [ -f "${range}${ext}.sql" ] || error "missing ${range}${ext}.sql"
+    done
+  done
 }
 
 @test "sql/ext_alpha--1.0.0.sql is generated" {