-
Notifications
You must be signed in to change notification settings - Fork 4
Fix the unable to locate element error #1065
Comments
Hello @satya7289 , may I work on this issue? |
Yes, please. I am assigning to you. |
Hey @satya7289 , thank you for assigning this issue to me. Do you have any specific fix in mind or should a |
Can I work on this issue as a part of OSH??Thank You. |
Can you do it with the implicit or explicit wait? |
yes, sure go ahead. I am assigning you too. |
can you assign this issue to me? |
Yes, sure. @Mahnoor123-Fatima |
@Nibba2018 @Anmollenka are you guys still working on it? |
@satya7289 I am not able to solve and cannot proceed. |
Sorry for my misunderstanding, I thought the issue was reassigned to @Anmollenka so I did not proceed further. Also I am assigned to the GitHub Auth issue so it's okay if it's assigned to someone else. |
Steps to reproduce this error ? Running test cases passed without an error! @satya7289 |
Sometimes it passes and sometimes not, this behaviour need to be fixed..! |
@Mahnoor123-Fatima , are you still working on it? |
I am willing to work and solve this issue. Please assign me the same |
Yes, @sujal111. I'm assigning you. |
How's the PR going? @sujal111 @Mahnoor123-Fatima |
I would like to work on this. Do assign if available. @satya7289 |
Initial PR #1126 made. Kindly have a look. @satya7289 |
Added the necessary Selenium explicit and implicit waits for automating the process without Travis CI failing for not locating elements. This will fix #1065.
Description
As a developer,
I need to pass Travis ci all the time if everything went well.
Mocks
Some time due to more traffic or some other reason, The Travis CI failed due to this error.
Acceptance Criteria
Definition of Done
Estimation
8-10 hours
The text was updated successfully, but these errors were encountered: