test: Apply suggested fix to tests/aes_encryption.rs

[Pr0methean]

This PR applies 1/5 suggestions from code quality AI findings. 4 suggestions were skipped to avoid creating conflicts.

[gemini-code-assist]

Summary of Changes

Hello @Pr0methean, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing code quality and readability within the test suite. It implements a specific suggestion from AI code quality findings by renaming a generic variable to a more descriptive one in several AES encryption test cases. This change aims to make the code easier to understand and maintain without altering its functional behavior.

Highlights

• Code Quality Improvement: Addressed one AI-identified code quality finding by improving variable naming for clarity.
• Refactoring: Refactored the variable name v to zip_data in four AES encryption test functions to enhance readability and expressiveness.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[amazon-q-developer]

This PR improves code readability by renaming the variable v to the more descriptive zip_data in four test functions. The changes are consistent and maintain the same functionality. The code compiles and functions correctly.

Note: The PR title should follow Conventional Commits format as specified in the project guidelines. Consider using a prefix like chore: or refactor: for this type of change.

---

You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

[gemini-code-assist]

Code Review

This pull request improves the variable naming in tests/aes_encryption.rs, which enhances readability. I've also identified an opportunity to simplify the code in these test functions. The current approach of creating a Vec, extending it from include_bytes!, and then creating a Cursor can be streamlined. My suggestions show how to create the ZipArchive more directly, which is more concise and avoids unnecessary allocations. This pattern is already used in other tests within the repository.