This repository has been archived by the owner on Jan 26, 2021. It is now read-only.
Fix: Fix Unable to locate element error #1150
Open
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
5 tasks
|
@satya7289 Do kindly provide your initial review on the PR, following I will be squashing the commits. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Added the necessary Selenium explicit and implicit waits for automating the process without Travis CI failing for not locating elements.
Fixes #1065
Type of Change:
Code/Quality Assurance Only
How Has This Been Tested?
All the Travis CI Checks passed after updating the code file.
Checklist:
Code/Quality Assurance Only