Add tests for the JUnitFormatter to disclose issues

The main issue is that the JUnitFormatter does not handle failures
in the before and after hooks properly. To add flexibility the tests
also specify that the JUnitFormatter should handle both all-steps-first
execution and one-step-at-the-time execution.

Author: brasmusson

core/src/main/java/cucumber/runtime/formatter/JUnitFormatter.java

@@ -46,6 +46,7 @@ class JUnitFormatter implements Formatter, Reporter, StrictAware {
 
     public JUnitFormatter(URL out) throws IOException {
         this.out = new UTF8OutputStreamWriter(new URLOutputStream(out));
+        TestCase.treatSkippedAsFailure = false;
         try {
             doc = DocumentBuilderFactory.newInstance().newDocumentBuilder().newDocument();
             rootElement = doc.createElement("testsuite");

core/src/test/java/cucumber/runtime/TestHelper.java

@@ -12,7 +12,7 @@
 
 @Ignore
 public class TestHelper {
-    static CucumberFeature feature(final String path, final String source) throws IOException {
+    public static CucumberFeature feature(final String path, final String source) throws IOException {
         ArrayList<CucumberFeature> cucumberFeatures = new ArrayList<CucumberFeature>();
         FeatureBuilder featureBuilder = new FeatureBuilder(cucumberFeatures);
         featureBuilder.parse(new Resource() {