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.

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

tests: More fixture rework, port test-diff to new path #258

Merged
merged 1 commit into from
Feb 28, 2022

Conversation

cgwalters
Copy link
Member

Currently the fixture is just built during cargo test; to help
debug it I wanted to support it being part of our main shared
library in the "integrationtest" path. For example I want to add
a CLI method to stand up the fixture directory (but not delete it).

But the other big thing going on here is that we now support updating
commits fully in memory, and so the diff API is ported to use this.

This requires ostreedev/ostree#2548

@cgwalters cgwalters force-pushed the test-fixture-ng5 branch 2 times, most recently from b9e5cc2 to 228ffc0 Compare February 28, 2022 15:59
@cgwalters
Copy link
Member Author

After this the next step is to port everything to the new fixture, and drop the hardcoded tarballs.

Currently the fixture is just built during `cargo test`; to help
debug it I wanted to support it being part of our main shared
library in the "integrationtest" path.  For example I want to add
a CLI method to stand up the fixture directory (but not delete it).

But the other big thing going on here is that we now support updating
commits fully in memory, and so the diff API is ported to use this.

This requires ostreedev/ostree#2548
Copy link
Member

@jmarrero jmarrero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@jmarrero jmarrero merged commit b05e9d4 into ostreedev:main Feb 28, 2022
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.

2 participants