Allow to specify profile when launching browsers #152
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Change ZestClientLaunch to allow to specify the path to a profile, used by Chrome and Firefox. Update tests to assert the new behaviour (serialisation and copy). Related to zaproxy/zaproxy#4339 - Option to launch browsers with specific profile
psiinon
approved these changes
Feb 7, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change ZestClientLaunch to allow to specify the path to a profile, used
by Chrome and Firefox.
Update tests to assert the new behaviour (serialisation and copy).
Related to zaproxy/zaproxy#4339 - Option to launch browsers with
specific profile