You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, when the [FeatureFile] attribute is missing, the framework finds the feature file in the base folder. By looking at the class namespace, it could also check the subfolder, assuming that the class namespace follows the folder structure.
The text was updated successfully, but these errors were encountered:
There is also a chance that this will cause confusion because not everybody follows the namespace-by-folder convention. Maybe I need to make the [FeatureFile] attribute required instead? So that way it always specifies where exactly the file is. Needs further thought/discussion.
By default, when the
[FeatureFile]
attribute is missing, the framework finds the feature file in the base folder. By looking at the class namespace, it could also check the subfolder, assuming that the class namespace follows the folder structure.The text was updated successfully, but these errors were encountered: