Skip to content

Tests are based on pytest #192

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.

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

Merged

Conversation

dmitry-lipetsk
Copy link
Collaborator

Usage of unittest was removed.

dmitry-lipetsk and others added 30 commits February 23, 2025 21:43
run tests through pytest explicitly
- TestgresRemoteTests does not use global variables and code
- Explicit work with ..testgres folder
It is required for tests.
Let's send warning about a garbage in the container "bound_ports" and continue working.
(cherry picked from commit fec1e7a)
This reverts commit 537a9ac.
It works now (was runned with a fresh probackup2 and vanilla 18devel).
Probackup plugin tests
 - They are skipped if PGPROBACKUPBIN is not defined

Global variable init_params is None when PGPROBACKUPBIN is not defined or version is not processed
Enumeration of all the known folders with tests.
Multiple attempts and logging are added.
Multiple attempts are added.
@dmitry-lipetsk
Copy link
Collaborator Author

dmitry-lipetsk commented Feb 26, 2025

This patch was tested locally (ubuntu 24.04), with probackup2 and was tested here with github CI many times.

I offer to merge now.

All the problems with test work through SSH (Remote) will be fixed in the next iterations.

@dmitry-lipetsk dmitry-lipetsk merged commit 0eeb705 into postgrespro:master Feb 26, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant