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.
19 lines
582 B
Python
19 lines
582 B
Python
from fixtures.zenith_fixtures import ZenithEnv
|
|
from fixtures.log_helper import log
|
|
|
|
pytest_plugins = ("fixtures.zenith_fixtures")
|
|
|
|
|
|
def test_pgbench(zenith_simple_env: ZenithEnv, pg_bin):
|
|
env = zenith_simple_env
|
|
# Create a branch for us
|
|
env.zenith_cli(["branch", "test_pgbench", "empty"])
|
|
|
|
pg = env.postgres.create_start('test_pgbench')
|
|
log.info("postgres is running on 'test_pgbench' branch")
|
|
|
|
connstr = pg.connstr()
|
|
|
|
pg_bin.run_capture(['pgbench', '-i', connstr])
|
|
pg_bin.run_capture(['pgbench'] + '-c 10 -T 5 -P 1 -M prepared'.split() + [connstr])
|