Closed daczczcz1 closed 6 years ago
The null pointer exception is thrown in the TestSourcesModel
class, which is part of the Cucumber code base, not the Serenity code base. It happens when the Serenity runner is used, because the Serenity reporter parses the feature file, but the bug is definitely inside the Cucumber code - the Cucumber parser throws a null pointer rather than raising a syntax error if no feature name is found.
Serenity now catches this exception and reports that the feature file was ignored.
Thank you for a very fast response! I'll forward your observation to the Cucumber team.
Summary
Expected Behavior
Current Behavior This is the stack trace:
Possible Solution
Steps to Reproduce (for bugs)
Runner:
Add an empty .feature file
Context & Motivation
I found the problem cause straight away, since I was working on some new test cases. However, if these would have been changes introduced by another user in a big team, the time spent troubleshooting could be significantly longer.
I first addressed this issue to the Cucumber project. They found out that this is a problem with Serenity-BDD. They provided a project that helped find out the cause: https://github.com/mlvandijk/npeissue