Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: web-3.1
-
Fix Version/s: 3.2
-
Component/s: Web Selenium
-
Labels:None
-
Number of attachments :
Description
new WebDriverProvider() { public void initialize() { throw new RuntimeException(); // or Error or something } }
... does not get reported. It's consumed because of a later NPE
The NPE is in StoryRunner, concerning member variable 'reporter' which is not set before use, in this situation.
Activity

Field | Original Value | New Value |
---|---|---|
Fix Version/s | 3.2 [ 16757 ] | |
Affects Version/s | web-3.1 [ 16756 ] | |
Affects Version/s | 3.2 [ 16757 ] |

Fix Version/s | 3.3 [ 17108 ] | |
Fix Version/s | 3.2 [ 16757 ] |

Fix Version/s | 3.x [ 16979 ] | |
Fix Version/s | 3.3 [ 17108 ] |

Component/s | Core [ 11086 ] | |
Component/s | Web Selenium [ 14124 ] |

Summary | Error in WebDriverProvider intialize method ignored because of consequential NPE for StoryRunner.reporter | Error in WebDriverProvider initialize method causes NPE in StoryRunner |
Fix Version/s | web-3.3 [ 17272 ] | |
Fix Version/s | 3.x [ 16979 ] | |
Component/s | Web Selenium [ 14124 ] | |
Component/s | Core [ 11086 ] |

Summary | Error in WebDriverProvider initialize method causes NPE in StoryRunner | Error in WebDriverProvider initialize method ignored due to NPE in StoryRunner |

Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |

Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |

Status | Reopened [ 4 ] | Closed [ 6 ] |
Fix Version/s | 3.2 [ 16757 ] | |
Fix Version/s | web-3.3 [ 17272 ] | |
Resolution | Fixed [ 1 ] |
See the Etsy tutorial. If you change the WebDriver sys-prop to 'DoesNotExist' and run the tests, you'll get the NPE described in this bug report.
It is because new FirefoxDriver() fails during the initialize() of WebDriverProvider as described, but that is totally hidden by a reference to StoryRunner.runner being null and causing a NPE.