This repository has been archived by the owner on Jun 12, 2021. It is now read-only.

Better exception message when the currently executing thread is not in a step definition context #630

Open

adamralph opened this issue Oct 30, 2019 · 0 comments

Labels

Milestone

Owner

adamralph commented Oct 30, 2019

This exception was introduced in 2.4.1.

As suggested by @BrunoJuchli in #617 (comment), the exception message should also contain hints about why this might be the case. E.g.

The currently executing thread is not a step definition context. For example, the step may be nested within another step, which is unsupported, or it may exist outside a scenario or background method.

adamralph added the enhancement label

adamralph added this to the 2.4.100 milestone

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.