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

test: purl2cpe database #4280

Merged
merged 3 commits into from
Jul 30, 2024
Merged

test: purl2cpe database #4280

merged 3 commits into from
Jul 30, 2024

Conversation

inosmeet
Copy link
Contributor

inosmeet added 2 commits July 23, 2024 10:09
Signed-off-by: Meet Soni <meetsoni3017@gmail.com>
Signed-off-by: Meet Soni <meetsoni3017@gmail.com>
Copy link
Contributor

@terriko terriko left a comment

Choose a reason for hiding this comment

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

Hm. I think you're right that we need a network test for coverage purposes, but I feel like we also could use a similar test against the local cache. My brain is fried from vacation: do we already have a similar test against the local cache or should we refactor to make this work locally or against a new network downloaded db?

Signed-off-by: Meet Soni <meetsoni3017@gmail.com>
Copy link
Contributor

@terriko terriko left a comment

Choose a reason for hiding this comment

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

This looks like it'll work. I love the way you handled the parameterization with the internal/external test difference.

@terriko terriko merged commit 58ba0b7 into intel:main Jul 30, 2024
22 checks passed
@inosmeet inosmeet deleted the test-purl2cpe branch August 13, 2024 05:21
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