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

[oss] Consolidate the integration test repos to a single one #676

Open
eskultety opened this issue Oct 4, 2024 · 0 comments
Open

[oss] Consolidate the integration test repos to a single one #676

eskultety opened this issue Oct 4, 2024 · 0 comments
Milestone
Become an indepen...

Comments

@eskultety
Copy link
Member

Currently, we use several test repos - at least one for each package manager backend we support (often more than that) which creates the confusion of what repos should new integration tests go to (a repo might not exist yet). There's also the factor of a small overhead of each integration test cloning a particular repository and creating network traffic.
If we could consolidate all test cases under a single repository and create dedicated branches for every test case it would at least clear up the confusion and help with consistency.
slimreaper35 added a commit to slimreaper35/cachi2 that referenced this issue Jan 16, 2025
@slimreaper35
integration tests: Use single test repository
6c2cb3e 
Modify each test module to use a branch (not a git commit) as a
reference inside the new integration test repository that contains all
integration (e2e) tests for cachi2.

Update and improve a few functions inside utils.py

Drop unnecessary lines from each Containerfile that were blindly
duplicated along with the comments. Plus, they were tightly coupled with
our code printing output of specific files inside of directories coming
from pytest.

closes containerbuildsystem#676

Signed-off-by: Michal Šoltis <msoltis@redhat.com>
slimreaper35 added a commit to slimreaper35/cachi2 that referenced this issue Jan 16, 2025
@slimreaper35
integration tests: Use single test repository
4761b3b 
Modify each test module to use a branch (not a git commit) as a
reference inside the new integration test repository that contains all
integration (e2e) tests for cachi2.

Update and improve a few functions inside utils.py

Drop unnecessary lines from each Containerfile that were blindly
duplicated along with the comments. Plus, they were tightly coupled with
our code printing output of specific files inside of directories coming
from pytest.

closes containerbuildsystem#676

Signed-off-by: Michal Šoltis <msoltis@redhat.com>
slimreaper35 added a commit to slimreaper35/cachi2 that referenced this issue Jan 16, 2025
@slimreaper35
integration tests: Use single test repository
2554af4 
Modify each test module to use a branch (not a git commit) as a
reference inside the new integration test repository that contains all
integration (e2e) tests for cachi2.

Update and improve a few functions inside utils.py

Drop unnecessary lines from each Containerfile that were blindly
duplicated along with the comments. Plus, they were tightly coupled with
our code printing output of specific files inside of directories coming
from pytest.

closes containerbuildsystem#676

Signed-off-by: Michal Šoltis <msoltis@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Become an independent OSS project
Development

No branches or pull requests
1 participant
@eskultety