Skip to content

Fixing device loading issue in Web mode#4069

Merged
Maheshkale447 merged 3 commits into
Releases/Betafrom
Mobile-Enhancments-and-Changes
Jan 22, 2025
Merged

Fixing device loading issue in Web mode#4069
Maheshkale447 merged 3 commits into
Releases/Betafrom
Mobile-Enhancments-and-Changes

Conversation

@MeniKadosh1

@MeniKadosh1 MeniKadosh1 commented Jan 21, 2025

Copy link
Copy Markdown
Contributor

Thank you for your contribution.
Before submitting this PR, please make sure:

  • PR description and commit message should describe the changes done in this PR
  • Verify the PR is pointing to correct branch i.e. Release or Beta branch if the code fix is for specific release , else point it to master
  • Latest Code from master or specific release branch is merged to your branch
  • No unwanted\commented\junk code is included
  • No new warning upon build solution
  • Code Summary\Comments are added to my code which explains what my code is doing
  • Existing unit test cases are passed
  • New Unit tests are added for your development
  • Sanity Tests are successfully executed for New and Existing Functionality
  • Verify that changes are compatible with all relevant browsers and platforms.
  • After creating pull request there should not be any conflicts
  • Resolve all Codacy comments
  • Builds and checks are passed before PR is sent for review
  • Resolve code review comments
  • Update the Help Library document to match any feature changes

Summary by CodeRabbit

  • New Features

    • Introduced a new input panel for setting context in the mobile device edit page.
    • Added functionality to retrieve and set available contexts for the mobile driver.
    • Expanded mobile device action capabilities with new actions for context management.
  • Bug Fixes

    • Improved error handling in mobile driver window title setting.
    • Enhanced control visibility for web application types.
  • Refactor

    • Clarified Selenium driver initialization and property assignment in Appium driver.
    • Improved code readability in mobile driver components.
    • Standardized parameter naming for Kobiton capabilities in device configuration.

@coderabbitai

coderabbitai Bot commented Jan 21, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

The pull request introduces changes across several files in the Ginger project. In MobileDriverWindow.xaml.cs, the SetTitle method has been updated to include a try-catch block for improved error handling, while the AlloworDisableControls method has been modified to conditionally hide buttons for web applications. The GenericAppiumDriver.cs file sees a refactor for the initialization of mSeleniumDriver, enhancing clarity. Additionally, ActMobileDeviceEditPage.xaml and its code-behind have been updated to include a new input panel for setting contexts, and new actions have been added to manage mobile device contexts.

Changes

File Change Summary
Ginger/Ginger/Drivers/DriversWindows/MobileDriverWindow.xaml.cs - Added try-catch block in SetTitle method for error handling
- Modified AlloworDisableControls to hide buttons for web applications
Ginger/GingerCoreNET/Drivers/CoreDrivers/Mobile/Appium/GenericAppiumDriver.cs - Repositioned comment for mSeleniumDriver initialization
- Separated StopProcess property assignment from object initializer
- Added cases for GetAvailableContexts and SetContext in mobile device actions
Ginger/Ginger/Actions/ActionEditPages/ActMobileDeviceEditPage.xaml - Added new StackPanel, Label, and UCValueExpression for user input
Ginger/Ginger/Actions/ActionEditPages/ActMobileDeviceEditPage.xaml.cs - Initialized xInputVE in BindControls
- Added visibility control for xInputPnl based on selected action
Ginger/Ginger/Drivers/DriversConfigsEditPages/AppiumDriverEditPage.xaml.cs - Updated parameter names for Kobiton capabilities with "kobiton:" prefix and added backward compatibility
Ginger/GingerCoreNET/ActionsLib/UI/Mobile/ActMobileDevice.cs - Added new property ActionInput
- Added enumerations GetAvailableContexts and SetContext

Possibly related PRs

Suggested reviewers

  • Maheshkale447

Poem

🐰 A Rabbit's Code Review Rhyme 🐰

In Ginger's realm, where drivers roam,
Error handling finds a new home.
Buttons hide, titles shine bright,
With try-catch magic, code takes flight!
A cleaner path, a smoother ride,
New contexts await, let’s take pride!


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

…e Action

2- Added "kobiton" prefix in Agent page

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f0168a5 and fbbe540.

📒 Files selected for processing (5)
  • Ginger/Ginger/Actions/ActionEditPages/ActMobileDeviceEditPage.xaml (1 hunks)
  • Ginger/Ginger/Actions/ActionEditPages/ActMobileDeviceEditPage.xaml.cs (3 hunks)
  • Ginger/Ginger/Drivers/DriversConfigsEditPages/AppiumDriverEditPage.xaml.cs (2 hunks)
  • Ginger/GingerCoreNET/ActionsLib/UI/Mobile/ActMobileDevice.cs (2 hunks)
  • Ginger/GingerCoreNET/Drivers/CoreDrivers/Mobile/Appium/GenericAppiumDriver.cs (2 hunks)
👮 Files not reviewed due to content moderation or server errors (4)
  • Ginger/Ginger/Actions/ActionEditPages/ActMobileDeviceEditPage.xaml
  • Ginger/Ginger/Actions/ActionEditPages/ActMobileDeviceEditPage.xaml.cs
  • Ginger/GingerCoreNET/ActionsLib/UI/Mobile/ActMobileDevice.cs
  • Ginger/GingerCoreNET/Drivers/CoreDrivers/Mobile/Appium/GenericAppiumDriver.cs
🔇 Additional comments (1)
Ginger/Ginger/Drivers/DriversConfigsEditPages/AppiumDriverEditPage.xaml.cs (1)

227-230: LGTM! Good standardization of Kobiton parameter names.

The parameter names are now properly prefixed with "kobiton:" which aligns with Kobiton's naming conventions.

Comment on lines +537 to 544
DeleteCapabilityIfExist("kobiton:username");
DeleteCapabilityIfExist("kobiton:accessKey");
DeleteCapabilityIfExist("kobiton:sessionName");
DeleteCapabilityIfExist("kobiton:deviceGroup");

//for backward support
DeleteCapabilityIfExist("username");
DeleteCapabilityIfExist("accessKey");

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🧹 Nitpick (assertive)

Consider refactoring the deletion logic for better maintainability.

The current implementation handles both new and old parameter names separately. Consider using a mapping to reduce duplication and improve maintainability.

Here's a suggested refactor:

-            DeleteCapabilityIfExist("kobiton:username");
-            DeleteCapabilityIfExist("kobiton:accessKey");
-            DeleteCapabilityIfExist("kobiton:sessionName");
-            DeleteCapabilityIfExist("kobiton:deviceGroup");
-
-            //for backward support
-            DeleteCapabilityIfExist("username");
-            DeleteCapabilityIfExist("accessKey");
-            DeleteCapabilityIfExist("sessionName");
-            DeleteCapabilityIfExist("deviceGroup");
+            var kobitonParams = new[] {
+                "username",
+                "accessKey",
+                "sessionName",
+                "deviceGroup"
+            };
+            
+            foreach (var param in kobitonParams)
+            {
+                DeleteCapabilityIfExist($"kobiton:{param}"); // Delete new format
+                DeleteCapabilityIfExist(param);              // Delete old format (backward support)
+            }
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
DeleteCapabilityIfExist("kobiton:username");
DeleteCapabilityIfExist("kobiton:accessKey");
DeleteCapabilityIfExist("kobiton:sessionName");
DeleteCapabilityIfExist("kobiton:deviceGroup");
//for backward support
DeleteCapabilityIfExist("username");
DeleteCapabilityIfExist("accessKey");
var kobitonParams = new[] {
"username",
"accessKey",
"sessionName",
"deviceGroup"
};
foreach (var param in kobitonParams)
{
DeleteCapabilityIfExist($"kobiton:{param}"); // Delete new format
DeleteCapabilityIfExist(param); // Delete old format (backward support)
}

@Maheshkale447
Maheshkale447 merged commit dab0a65 into Releases/Beta Jan 22, 2025
@Maheshkale447
Maheshkale447 deleted the Mobile-Enhancments-and-Changes branch January 22, 2025 07:39
@coderabbitai coderabbitai Bot mentioned this pull request Feb 2, 2025
15 tasks
@coderabbitai coderabbitai Bot mentioned this pull request Feb 10, 2025
15 tasks
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