
|
If you were logged in you would be able to see more operations.
|
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
http://forums.openqa.org/thread.jspa?threadID=10173
verifyTrue and verifyFalse methods don't have the versions, which take the messages. Because checkForVerificationErrors throws an exception which only tells you, that some verify... method has failed, if you have more than one, you can't tell, which was it. To make the verifyTrue(String message,Boolean condition) version i've had to break in to the private field of the SeleneseTestCase class. And that is not a nice coding practice. If the StringBuffer verificationErrors field was protected field it would make verify... methods a lot more flexible.
|
|
Description
|
http://forums.openqa.org/thread.jspa?threadID=10173
verifyTrue and verifyFalse methods don't have the versions, which take the messages. Because checkForVerificationErrors throws an exception which only tells you, that some verify... method has failed, if you have more than one, you can't tell, which was it. To make the verifyTrue(String message,Boolean condition) version i've had to break in to the private field of the SeleneseTestCase class. And that is not a nice coding practice. If the StringBuffer verificationErrors field was protected field it would make verify... methods a lot more flexible. |
Show » |
| There are no comments yet on this issue.
|
|