Adding short stack traces as an option #227
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
+1 Any idea when this feature will be merged. |
|
+1 |
Purpose
=======
This is designed to make the filesystem layout and arrangement of features
more flexible. Target audience is larger projects with multiple
developers.
Changes:
- Throws errors if more than one step definition matches a feature step.
- Small fixes for file path matching in Windows.
- Special tag format for selecting which files are used for steps.
The special tags are designed to be used where the `-r` tag is specified.
They should work where file name matching is done, but will be less
useful.
Tags
====
If no source tags are set, default behaviour is used: all matching step
definitions will be used to fulfill a step.
If one or more file source tags are set in a file, then only the
specified sources are used. Sources accumulate, so each tag ADDS to the
available pool of definitions.
Tags are inherited, so setting at a feature level sets for all
scenarios.
Specific named file tags don't use path or `.js` ending. Files with the
matching name will be allowed as step definitions:
@:MySteps
Will match (e.g.)
./step_definitions/MySteps.js
./step_definitions/specific/path/MySteps.js
Directory path tags match against the end of the step files' path.
This is non-recursive, so child directories will not be used.
@./Interpretation
Will match
./step_definition/Interpretation/x.js
./step_definition/Interpretation/y.js
./step_definition/deeper/Interpretation/x.js
But not
./step_definition/Interpretation/deeper/y.js
Any steps loaded from {step path}/support/ will be included
regardless of tags
…e supplied primary key. Note: Method assumes the first cell in a row is the primary key
Updated the table object to include a function that gets the entire row for where the first cell matches a value Merge remote-tracking branch 'andy/master' into sigmaNPM
…nt once all the support files are loaded. Command line option is : brkOnSupportCodeLoaded
Table querying
Closes cucumber#3 Includes source mapping. Probably won't map minified outputs well.
Closes cucumber#4 Requires grunt-cucumber-sigma 0.3.3+
Closes cucumber#5 Adds a `deferredStep` definition which makes any scenario containing it run after all non-deferred scenarios.
|
Thanks @AndrewJohnBenjamin for this. The short stack traces are now implemented (see f584233). There are several other features in this PR. Please open new, separate, PRs for those. |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated the package to include a command line option that allows the user to specify whether or not they would like single line stack traces upon step failure.
Currently the stack traces that are output by the package in the event of a step failure are pretty large and make it a little more difficult to see what has failed. The changes I have made cut this trace down to a single line and shows only the line in the code that caused the step to fail.
The changes involved slight modifications to runtime, configuration, argument parser and step_definition.
I believe this addition would benefit others as it seems this issue has been flagged already.
#157