Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Minor
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 3.1.0.Beta4
-
Labels:None
Description
All the test failures are caused by weird behavior of the selenium.getAlert() method, which does not detect the alert after a remoting call. Alerts produced directly seem to be detected as expected.
remoting/helloworld:
Tests in error:
|
testCasualEnglish(org.jboss.seam.remoting.examples.helloworld.ftest.HelloworldTest): ERROR: There were no alerts
|
testCasualRussian(org.jboss.seam.remoting.examples.helloworld.ftest.HelloworldTest): ERROR: There were no alerts
|
testFormalEnglish(org.jboss.seam.remoting.examples.helloworld.ftest.HelloworldTest): ERROR: There were no alerts
|
testFormalRussian(org.jboss.seam.remoting.examples.helloworld.ftest.HelloworldTest): ERROR: There were no alerts
|
|
|
Tests run: 4, Failures: 0, Errors: 4, Skipped: 0
|
|
|
remoting/validation
|
|
|
Tests in error:
|
testCorrectValues(org.jboss.seam.remoting.examples.validation.ftest.ValidationTest): ERROR: There were no alerts
|
|
|
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0
|
Gliffy Diagrams
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
