mirror of
https://github.com/neondatabase/neon.git
synced 2025-12-26 15:49:58 +00:00
66ec135676
Instead of having a lot of separate fixtures for setting up the page server, the compute nodes, the safekeepers etc., have one big ZenithEnv object that encapsulates the whole environment. Every test either uses a shared "zenith_simple_env" fixture, which contains the default setup of a pageserver with no authentication, and no safekeepers. Tests that want to use safekeepers or authentication set up a custom test-specific ZenithEnv fixture. Gathering information about the whole environment into one object makes some things simpler. For example, when a new compute node is created, you no longer need to pass the 'wal_acceptors' connection string as argument to the 'postgres.create_start' function. The 'create_start' function fetches that information directly from the ZenithEnv object.
34 lines
958 B
Python
34 lines
958 B
Python
import pytest
|
|
import os
|
|
|
|
from fixtures.zenith_fixtures import ZenithEnv
|
|
from fixtures.log_helper import log
|
|
|
|
pytest_plugins = ("fixtures.zenith_fixtures")
|
|
"""
|
|
Use this test to see what happens when tests fail.
|
|
|
|
We should be able to clean up after ourselves, including stopping any
|
|
postgres or pageserver processes.
|
|
|
|
Set the environment variable RUN_BROKEN to see this test run (and fail,
|
|
and hopefully not leave any server processes behind).
|
|
"""
|
|
|
|
run_broken = pytest.mark.skipif(os.environ.get('RUN_BROKEN') is None,
|
|
reason="only used for testing the fixtures")
|
|
|
|
|
|
@run_broken
|
|
def test_broken(zenith_simple_env: ZenithEnv, pg_bin):
|
|
env = zenith_simple_env
|
|
|
|
# Create a branch for us
|
|
env.zenith_cli(["branch", "test_broken", "empty"])
|
|
|
|
env.postgres.create_start("test_broken")
|
|
log.info('postgres is running')
|
|
|
|
log.info('THIS NEXT COMMAND WILL FAIL:')
|
|
pg_bin.run('pgbench -i_am_a_broken_test'.split())
|