-
Notifications
You must be signed in to change notification settings - Fork 1
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
- Status: Open.#62 In Postgres-Extensions/pgxntool-test;
- Status: Open.#49 In Postgres-Extensions/pgxntool-test;
- Status: Open.#47 In Postgres-Extensions/pgxntool-test;
Investigate: standardize the make -n dry-run-parsing pattern (and check for an existing BATS/Makefile-testing tool)
investigationOpen research/investigation, not a mandated changeOpen research/investigation, not a mandated changeStatus: Open.#46 In Postgres-Extensions/pgxntool-test;Investigate: replace ad-hoc mktemp usage with BATS_TEST_TMPDIR where appropriate
investigationOpen research/investigation, not a mandated changeOpen research/investigation, not a mandated changeStatus: Open.#45 In Postgres-Extensions/pgxntool-test;Research: is bats-assert/bats-support adoption worth it (possibly as a submodule, like bats-core)?
investigationOpen research/investigation, not a mandated changeOpen research/investigation, not a mandated changeStatus: Open.#44 In Postgres-Extensions/pgxntool-test;- Status: Open.#41 In Postgres-Extensions/pgxntool-test;
- Status: Open.#38 In Postgres-Extensions/pgxntool-test;
- Status: Open.#13 In Postgres-Extensions/pgxntool-test;
Test suite performance: per-suite breakdown and reordering opportunities
performancePerformance analysis or optimizationPerformance analysis or optimizationStatus: Open.#11 In Postgres-Extensions/pgxntool-test;Test suite performance analysis (Linux container, with Postgres)
performancePerformance analysis or optimizationPerformance analysis or optimizationStatus: Open.#10 In Postgres-Extensions/pgxntool-test;