Skip to content

Conversation

TroyWalshProf
Copy link
Contributor

Change list

Users will need to be able to provide a browser name if they want to run automation against a mobile web browser.
To facilitate this we will be allowing users to set the BrowserName property in AppiumOptions.

To test this, Appium will need the correct version of the associated driver
If you want Appium to figure out what version you need you can run Appium with this command: appium --allow-insecure chromedriver_autodownload

Types of changes

What types of changes are you proposing/introducing to .NET client?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • New feature (non-breaking change which adds value to the project)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Documentation

  • Have you proposed a file change/ PR with appium to update documentation?

This can be done by navigating to the documentation section on http://appium.io selecting the appropriate command/endpoint and clicking the 'Edit this doc' link to update the C# example

Integration tests

  • Have you provided integration tests to pass against the beta version of appium? (for Bugfix or New feature)

@TroyWalshProf
Copy link
Contributor Author

@akinsolb - Another small change to restore functionality lost with the Selenium 4 transition

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants