[JBoss JIRA] Created: (WELD-306) Errors thrown by lifecycle events or added to lifecycle events aren't being reported
by Pete Muir (JIRA)
Errors thrown by lifecycle events or added to lifecycle events aren't being reported
------------------------------------------------------------------------------------
Key: WELD-306
URL: https://jira.jboss.org/jira/browse/WELD-306
Project: Weld
Issue Type: Bug
Components: Bootstrap and Metamodel API
Reporter: Pete Muir
*.deployment.lifecycle.broken.addDefinitionError.AddDefinitionErrorTest.testObserverDefinitionErrorTreatedAsDefinitionError
*.deployment.lifecycle.broken.addDeploymentProblem.AddDeploymentProblemTest.testObserverDeploymentProblemTreatedAsDeploymentError
*.deployment.lifecycle.broken.exeptionInAfterBeanDiscoveryObserver.AfterBeanDiscoveryObserverExecutionFailureTest.testObserverFailureTreatedAsDefinitionError
*.deployment.lifecycle.broken.exeptionInAfterBeanValidationObserver.AfterDeploymentValidationObserverExecutionFailureTest.testObserverFailureTreatedAsDeploymentError
Weld is not rethrowing the exceptions due to incorrectly overridden fire method
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (WELD-368) Modify functional tests to use Surefire/Failsafe plugin
by Karel Piwko (JIRA)
Modify functional tests to use Surefire/Failsafe plugin
-------------------------------------------------------
Key: WELD-368
URL: https://jira.jboss.org/jira/browse/WELD-368
Project: Weld
Issue Type: Task
Components: Testing Infrastructure (Mocks and Harness Integration)
Affects Versions: 1.0.0.CR1
Reporter: Karel Piwko
Assignee: Karel Piwko
Fix For: 1.0.1.CR1
When running functional test inside of Maven Antrun plugin, whatever the results are, control flow continues. Additionally, the resulting summary for each example is not visible.
The decision was to migrate functionality to Failsafe plugin, because it grants undeploying the archive/stopping Selenium server even if integration testing itself fails. Failsafe acts as Surefire, so its reports are familiar to other developers.
If functional testing fails, Maven ends up with failure message. This is the intended behavior.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months