fix test data

[matthyx]

Type

bug_fix

---

Description

This PR includes updates to the test data in several test files. The changes include:

• Updated the expected DB version in Test_grypeAdapter_DBVersion function in grype_test.go.
• Updated the expected source ID in Test_domainJSONToSyft function in domain_to_syft_test.go.
• Updated various fields in the test data in hello-world-sbom.format.json.
• Updated the checksum in alpine-cve.json and listing.json.

---

PR changes walkthrough

Relevant files

Tests

5 files grype_test.go                                                                                              adapters/v1/grype_test.go **The test data in the `Test_grypeAdapter_DBVersion` function was updated. The expected DB version was changed.** +1/-1 domain_to_syft_test.go                                                                            adapters/v1/domain_to_syft_test.go **The test data in the `Test_domainJSONToSyft` function was updated. The expected source ID was changed.** +1/-1 hello-world-sbom.format.json                                                                adapters/v1/testdata/hello-world-sbom.format.json **The test data in the file was updated. Changes include the source ID, image ID, manifest digest, image size, digest, size, manifest, and config.** +9/-9 alpine-cve.json                                                                                          adapters/v1/testdata/alpine-cve.json **The test data in the file was updated. The checksum was changed.** +1/-1 listing.json                                                                                                adapters/v1/testdata/listing.json **The test data in the file was updated. The checksum was changed.** +1/-1

[codiumai-pr-agent-free[bot]]

PR Description updated to latest commit (https://github.com/kubescape/kubevuln/commit/4e2ad36791a0ab6df59667cfcc474e615687f112)

[codiumai-pr-agent-free[bot]]

PR Analysis

• 🎯 Main theme: Updating test data
• 📝 PR summary: This PR updates the test data in several test files. The changes include updating the expected DB version, source ID, various fields in the test data, and checksums.
• 📌 Type of PR: Bug fix
• 🧪 Relevant tests added: No
• ⏱️ Estimated effort to review [1-5]: 1, because the changes are straightforward and involve only updating test data.
• 🔒 Security concerns: No security concerns found

  PR Feedback

💡 General suggestions: It's good to see that the test data is being kept up-to-date. This is crucial for maintaining the accuracy of the tests. However, it would be beneficial to provide more context in the PR description about why these specific changes were made. For example, was there a change in the application code that necessitated these updates? Understanding the reason behind the changes can help reviewers provide more insightful feedback.

🤖 Code feedback:

---

relevant file	adapters/v1/grype_test.go
suggestion	Consider using a constant for the DB version hash to avoid hardcoding it in the test. This can make it easier to update in the future. [medium]
relevant line	assert.Equal(t, "sha256:9be2df3d7d657bfb40ddcc68c9d00520ee7f5a34c7a26333f90cf89cefd5668a", version)

---

relevant file	adapters/v1/domain_to_syft_test.go
suggestion	Similar to the previous suggestion, consider using a constant for the source ID to avoid hardcoding it in the test. [medium]
relevant line	id: "03a75d703fcd471cc09ed0dfffde55b74d95598343411e7fa3bcebc18d91bb8b",

---

relevant file	adapters/v1/testdata/hello-world-sbom.format.json
suggestion	If this test data is used in multiple tests, consider creating a helper function to generate it. This can make the tests more maintainable and less prone to errors. [medium]
relevant line	"id": "03a75d703fcd471cc09ed0dfffde55b74d95598343411e7fa3bcebc18d91bb8b",

---

relevant file	adapters/v1/testdata/alpine-cve.json
suggestion	If possible, automate the process of updating the checksum in the test data. This can help prevent human error and save time. [medium]
relevant line	"checksum": "sha256:99ad9fd54be5295351555a02a0fb6986a461a9d23eb8ae3b34ea892c252a8c80",

---

✨ Usage tips:

---

> To invoke the PR-Agent, add a comment using one of the following commands: > - **/review**: Request a review of your Pull Request. > - **/describe**: Update the PR title and description based on the contents of the PR. > - **/improve [--extended]**: Suggest code improvements. Extended mode provides a higher quality feedback. > - **/ask \**: Ask a question about the PR. > - **/update_changelog**: Update the changelog based on the PR's contents. > - **/add_docs** 💎: Generate docstring for new components introduced in the PR. > - **/generate_labels** 💎: Generate labels for the PR based on the PR's contents. > - **/analyze** 💎: Automatically analyzes the PR, and presents changes walkthrough for each component. >See the [tools guide](https://github.com/Codium-ai/pr-agent/blob/main/docs/TOOLS_GUIDE.md) for more details. >To edit any configuration parameter from the [configuration.toml](https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml), add --config_path=new_value. >For example: /review --pr_reviewer.extra_instructions="focus on the file: ..." >To list the possible configuration parameters, add a **/config** comment.

[github-actions[bot]]

Summary:

• License scan: failure
• Credentials scan: success
• Vulnerabilities scan: failure
• Unit test: success
• Go linting: success