forked from karatelabs/karate
-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
Merge #1
Merged
Merged
Merge #1
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
so that the method signatures are easier to read for those viewing via readme / doc links
This reverts commit 88026a2
Jnuit4 parallel test runner
in the future, the netty picocli has to be merged and we also would have native html parallel reports but for now, we can start testing the vs code plugin for this parallel execution will now generate native html report and continuously update the results-json.txt which the plugin can read and update etc
the test results will have timings and logs associated correctly also using the unified karate short-syntax for scenario / line number etc
trust me it jst did not feel right with zero based indexing
and even beforeStep() afterStep()
does not support moving text cursor to end
added [webDriverUrl] key and some extra driver init logic and works fine against zalenium breaking change for some of the wip appium work see doc changes for all the details
also changes to what was discussed in #924 so now it is [webDriverSession] and not [webDriverCapabilities] so user has full control over the webdriver POST to /session payload - which will take care of any remote / saas situation and quirks of implementations like selenium grid introduced [httpConfig] key and now you can configure the http client e.g. readTimeout which is needed for aws as it can take a long time for a device / browser desktop to be provisioned see readme edits for details
especially the start life-cycle, better error detection and handling on session fail mobile / winappdriver breaking change for starting session, need to use [webDriverSession]
docker-target will pull only if flagged, and will remove container instance at end added nice test to check docker container locally in demo/driver/core chrome native will always wait for http to be ready
now you can set a base-path from which images will be loaded added readme to get things going
Bumps `netty.version` from 4.1.37.Final to 4.1.50.Final. Updates `netty-handler` from 4.1.37.Final to 4.1.50.Final - [Release notes](https://github.com/netty/netty/releases) - [Commits](netty/netty@netty-4.1.37.Final...netty-4.1.50.Final) Updates `netty-codec-http` from 4.1.37.Final to 4.1.50.Final - [Release notes](https://github.com/netty/netty/releases) - [Commits](netty/netty@netty-4.1.37.Final...netty-4.1.50.Final) Signed-off-by: dependabot[bot] <support@github.com>
…ty.version-4.1.50.Final Bump netty.version from 4.1.37.Final to 4.1.50.Final in /karate-core
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.
Description
Thanks for contributing this Pull Request. Make sure that you send in this Pull Request to the
develop
branch of this repository, add a brief description, and tag the relevant issue(s) and PR(s) below.