Skip to content

Commit

Permalink
Squashed dirty Spring features
Browse files Browse the repository at this point in the history
  • Loading branch information
Dmytro Chyzhykov committed Aug 23, 2013
1 parent c935592 commit 0f65ace
Show file tree
Hide file tree
Showing 3 changed files with 14 additions and 13 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -118,7 +118,6 @@ private String getMultipleExceptionMessage(Map<Class<?>, Exception> exceptionsTh
exceptionsThrown.append("Multiple exceptions occurred during processing of the TestExecutionListeners\n\n");

for (Map.Entry<Class<?>, Exception> classExceptionEntry : exceptionsThrow.entrySet()) {

exceptionsThrown.append("Exception during processing of TestExecutionListeners of ");
exceptionsThrown.append(classExceptionEntry.getKey());
exceptionsThrown.append('\n');
Expand Down
Original file line number Diff line number Diff line change
@@ -1,10 +1,22 @@
Feature: Dirty Cukes
Feature: Spring Dirty Cukes
In order to have a completely clean system for each scenario
As a purity activist
I want each dirty scenario to have its own application context

Scenario Outline: Eat some dirty cukes
Scenario Outline: Eat some annotated dirty cukes
Given I have <numberOfBeans> dirty cukes in my belly
Then there are <numberOfBeans> dirty cukes in my belly

Examples:
| numberOfBeans |
| 4 |
| 2 |

Scenario Outline: Eat some XML dirty beans
Given I have <numberOfBeans> dirty beans in my belly
Then there are <numberOfBeans> dirty beans in my belly

Examples:
| numberOfBeans |
| 4 |
| 2 |

This file was deleted.

0 comments on commit 0f65ace

Please sign in to comment.