| Key: |
SRC-403
|
| Type: |
Bug
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Mattias
|
| Votes: |
0
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Environment:
|
Win XP
|
|
|
Today we are using 0.9.0 and we have quite a few @selenium.is_element_present in our scripts. They are often used to control script behaviours, i.e. they returning false should not mean anything other than antoher direction is taken in our scripts.
When I tried 0.9.2 I noticed that if @selenium.is_element_present returns false a SeleniumCommandError is thrown and the whole script fails/stops. I've seen others writing about this problem aswell...
|
|
Description
|
Today we are using 0.9.0 and we have quite a few @selenium.is_element_present in our scripts. They are often used to control script behaviours, i.e. they returning false should not mean anything other than antoher direction is taken in our scripts.
When I tried 0.9.2 I noticed that if @selenium.is_element_present returns false a SeleniumCommandError is thrown and the whole script fails/stops. I've seen others writing about this problem aswell... |
Show » |
|
@selenium.is_element_present returns SeleniumCommandError