Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add automated test for pg_upgrade #224

Open
adamguo0 opened this issue Jul 25, 2023 · 1 comment
Open

Add automated test for pg_upgrade #224

adamguo0 opened this issue Jul 25, 2023 · 1 comment
Labels
test regression test to ensure future commits don't break existing functionality

Comments

@adamguo0
Copy link
Contributor

Describe the problem

We should make sure new changes to pg_tle do not break when they go through pg_upgrade.

Describe the proposal

We can potentially do this with a TAP test, but our tests are currently set up to run on a single version of Postgres. Will need to do more investigating
@adamguo0 adamguo0 added enhancement New feature or request test regression test to ensure future commits don't break existing functionality and removed enhancement New feature or request labels Jul 25, 2023
@jnasbyupgrade
Copy link

FYI you can find an example of how to do this at https://github.com/theory/pgtap/blob/main/test/test_MVU.sh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
test regression test to ensure future commits don't break existing functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@adamguo0 @jnasbyupgrade