Repository navigation
Nc/perf qs modernize - #1829
Nc/perf qs modernize#1829ncooke3 wants to merge 13 commits into
Conversation
This reverts commit f2dbe8a.
Summary of ChangesHello @ncooke3, I'm Gemini Code Assist1! 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 introduces a temporary modification to the performance UI tests by disabling a specific Highlights
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
The pull request temporarily disables a test case for the download functionality in UITests.swift with a TODO comment. This change should be tracked to ensure the test is re-enabled once the specified conditions are met, to maintain full test coverage.
| // TODO: Re-enable once iOS 18.4 sims are dropped. | ||
| // try checkFunctionality(function: download, startingStatus: .idle) |
There was a problem hiding this comment.
The checkFunctionality test for the download function has been temporarily disabled. While the TODO explains the reason, it's important to ensure that this test is re-enabled as soon as the iOS 18.4 simulator issue is resolved. Disabling tests, even temporarily, can lead to regressions if not properly tracked and restored. Consider creating a follow-up task or issue to ensure this is addressed.
No description provided.