Behat/Behat — Issue #65: Better notice descriptions
Author: awildeep
Created: 2011-10-27 21:00:09+00:00
State: open

When writing a context function if you have a syntax error like for instance a typo, it would be really nice to see a slightly more descriptive notice.

For example while working on a scenario context I got the following error:

```Notice: Undefined variable: typ```

The issue was that my variable should have been named `$type`, but I mistakenly set it to `$typ`.

Behat is smart enough to know there was an issue in the scenario, it would be ideal to be able to get a more verbose detail. I know this may not be a viable goal, but in a complex scenario syntax function it could be difficult to find a non-descriptive error.

(If you close this due to it not being possible, no problem. It is just a suggestion.)