Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Automation with local Safari browser profile does not work #86

Closed
mgnauck opened this issue May 3, 2019 · 3 comments
Closed

Automation with local Safari browser profile does not work #86

mgnauck opened this issue May 3, 2019 · 3 comments
Assignees
@occupant23 @mgnauck
Labels
bug codeDone The issue is rechecked for development branch codeReadyForRecheck The issue is fixed/implemented AND merged into development, but needs to be rechecked there docsReadyForMerge Documentation was created for this issue in a separate branch which is ready to merge to develop Medium Priority
Milestone
v3.3.0

Comments

@mgnauck
Copy link

mgnauck commented May 3, 2019

Selecting a local Safari(Driver) browser profile results in a NPE when executing the test. Safari and SafariDriver are available on the path (or, alternatively, paths were provided directly via the properties). Automation with other browsers works on the very same machine and project, as does automation with Safari(Driver) work in other, non-Neodymium projects.

Safari-Issue
@mgnauck mgnauck added the bug label May 3, 2019
@occupant23 occupant23 added this to the v3.3.0 milestone May 6, 2019
occupant23 pushed a commit that referenced this issue May 7, 2019
#86: Automation with local Safari browser profile does not work
8bdfea1
@occupant23
Copy link
Contributor

Added support in Neodymium.
Documentation needed add the following link to document the enabling process.

https://developer.apple.com/documentation/webkit/testing_with_webdriver_in_safari#2957277

@occupant23 occupant23 self-assigned this May 8, 2019
@occupant23 occupant23 added the codeReadyForRecheck The issue is fixed/implemented AND merged into development, but needs to be rechecked there label May 8, 2019
@occupant23 occupant23 added the docsReadyForMerge Documentation was created for this issue in a separate branch which is ready to merge to develop label Jun 3, 2019
@occupant23
Copy link
Contributor

added documentation to the development wiki

@mgnauck mgnauck added the codeDone The issue is rechecked for development branch label Jun 6, 2019
@mgnauck
Copy link
Author

mgnauck commented Jun 6, 2019

Tested successfully.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@occupant23 occupant23

@mgnauck mgnauck

Labels
bug codeDone The issue is rechecked for development branch codeReadyForRecheck The issue is fixed/implemented AND merged into development, but needs to be rechecked there docsReadyForMerge Documentation was created for this issue in a separate branch which is ready to merge to develop Medium Priority
Projects
None yet
Milestone
v3.3.0
Development

No branches or pull requests
2 participants
@occupant23 @mgnauck