-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #266 from akiellor/jruby-backtraces
Fix ignoring of JRuby backtraces.
- Loading branch information
Showing
3 changed files
with
38 additions
and
16 deletions.
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
Feature: Backtraces | ||
In order to discover errors quickly | ||
As a cuker | ||
I want to see backtraces for failures | ||
|
||
Background: | ||
Given a file named "features/failing_hard.feature" with: | ||
""" | ||
Feature: Sample | ||
Scenario: Example | ||
Given failing | ||
""" | ||
|
||
@jruby | ||
Scenario: Backtraces enabled | ||
Given a file named "features/step_definitions/steps.rb" with: | ||
""" | ||
require 'java' | ||
java_import 'java.util.Collections' | ||
Given /^failing$/ do | ||
Collections.empty_list.add 1 | ||
end | ||
""" | ||
When I run `cucumber features/failing_hard.feature` | ||
Then it should fail with: | ||
""" | ||
Feature: Sample | ||
Scenario: Example # features/failing_hard.feature:2 | ||
Given failing # features/step_definitions/steps.rb:4 | ||
java.lang.UnsupportedOperationException: null (NativeException) | ||
java/util/AbstractList.java:131:in `add' | ||
java/util/AbstractList.java:91:in `add' | ||
""" | ||
|
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