
| Key: |
SEL-292
|
| Type: |
Bug
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Patrice Neff
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
Selenium
Created: 22/Aug/06 11:05 AM
Updated: 16/Oct/06 02:07 AM
|
|
| Component/s: |
Waiting
|
| Affects Version/s: |
0.7.1
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Environment:
|
Firefox 1.5 on Mac
|
|
|
The new function Selenium.prototype.doWaitForCondition fails when the test raises an exception in the beginning. I often have tests that may raise exceptions until the state changes. While it might be possible to rewrite my tests, I think the proper solution is to ignore exceptions.
So I changed the currentTest.waitForCondition function as follows:
currentTest.waitForCondition = function () {
try {
return eval(script);
} catch (e) {
return false;
}
};
|
|
Description
|
The new function Selenium.prototype.doWaitForCondition fails when the test raises an exception in the beginning. I often have tests that may raise exceptions until the state changes. While it might be possible to rewrite my tests, I think the proper solution is to ignore exceptions.
So I changed the currentTest.waitForCondition function as follows:
currentTest.waitForCondition = function () {
try {
return eval(script);
} catch (e) {
return false;
}
};
|
Show » |
| There are no comments yet on this issue.
|
|