mirror of
https://github.com/neondatabase/neon.git
synced 2025-12-26 15:49:58 +00:00
b8d47b5acf
## Problem We currently don't run end-to-end tests for PostgreSQL extensions on our cloud infrastructure, which means we might miss problems that only occur in a real cloud environment. ## Summary of changes - Added a workflow to run extension tests against a cloud staging instance - Set up proper project configuration for extension testing - Implemented test execution with appropriate environment settings - Added error handling and reporting for test failures --------- Co-authored-by: Alexander Bayandin <alexander@neon.tech> Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
16 lines
578 B
Makefile
16 lines
578 B
Makefile
EXTENSION = pg_session_jwt
|
|
|
|
REGRESS = basic_functions
|
|
REGRESS_OPTS = --load-extension=$(EXTENSION)
|
|
export PGOPTIONS = -c pg_session_jwt.jwk={"crv":"Ed25519","kty":"OKP","x":"R_Abz-63zJ00l-IraL5fQhwkhGVZCSooQFV5ntC3C7M"}
|
|
|
|
PG_CONFIG ?= pg_config
|
|
PGXS := $(shell $(PG_CONFIG) --pgxs)
|
|
PG_REGRESS := $(dir $(PGXS))../../src/test/regress/pg_regress
|
|
.PHONY installcheck:
|
|
installcheck:
|
|
dropdb --if-exists contrib_regression
|
|
createdb contrib_regression
|
|
psql -d contrib_regression -c "CREATE EXTENSION $(EXTENSION)"
|
|
$(PG_REGRESS) --use-existing --dbname=contrib_regression $(REGRESS)
|