Issues
- Tests do not fail when Spring context fails to loadJBEHAVE-970Resolved issue: JBEHAVE-970
- using spring's <jdbc:embedded-database> tag calls the init script twiceJBEHAVE-936
- Support Spring AnnotationConfigApplicationContextJBEHAVE-754Resolved issue: JBEHAVE-754Mauro Talevi
- Add JBehave Spring Namespace support for easier configurationJBEHAVE-491Mauro Talevi
- SpringStoryReporterBuilder does not expose all properties in StoryReporterBuilderJBEHAVE-444Resolved issue: JBEHAVE-444
- SpringStepsFactory should ignore beans with undefined type and that fail instantiationJBEHAVE-349Resolved issue: JBEHAVE-349Mauro Talevi
- SpringStepsFactory should not try to instantiate abstract beansJBEHAVE-348Resolved issue: JBEHAVE-348Mauro Talevi
7 of 7
Tests do not fail when Spring context fails to load
Fixed
Description
Created December 17, 2013 at 1:18 PM
Updated March 11, 2014 at 7:09 AM
Resolved February 26, 2014 at 7:48 AM
Activity
Show:
When the creation of the Spring context fails, because resources cannot be found, beans cannot be created or some other configuration issue, the tests is not run but the result does not reflect this properly. Therefore Maven and Jenkins think tests are successful which gives a false positive. When nobody looks at the logs, nobody will see there is actually an error.
Cloned JBehave repo and fixed issue in: https://github.com/diversit/jbehave-core/commit/275f609a8faf2dfb2ee4feaa1be0351accbd9992