title: Karma E2E Tests found but skipped and marked as fail
body: <p>Given the e2e config:</p>
  <pre><code>module.exports = function(config) {
      config.set({
          basePath: '../',
  
          files: [
              'E2E/**/*.js'
          ],
  
          autoWatch: false,
  
          browsers: ['Chrome'],
  
          frameworks: ['ng-scenario'],
  
          singleRun: true,
  
          proxies: {
              '/': 'http://localhost:8000/'
          },
  
          plugins: [
              'karma-junit-reporter',
              'karma-chrome-launcher',
              'karma-jasmine',
              'karma-ng-scenario'
          ],
  
          junitReporter: {
              outputFile: 'test_out/e2e.xml',
              suite: 'e2e'
          },
  
          urlRoot: '/_karma_/'
      });
  };
  </code></pre>
  <p>and the scenario:</p>
  <pre><code>'use strict';
  
  /* http://docs.angularjs.org/guide/dev_guide.e2e-testing */
  
  describe('Mailing App', function () {
  
      it('should filter the phone list as user types into the search box', function () {
          expect(true).toBe(true);
      });
  
      it('should filter the phone list as user types into the search box', function () {
          expect(Element('foo').count()).toEqual(1);
      });
  
      describe('Sample Test', function () {
  
          beforeEach(function () {
              browser().navigateTo('../../Client/Views/Shared/_Layout.cshtml');
          });
  
          it('should filter the phone list as user types into the search box', function () {
              pause();
              expect(Element('.ng-binding')).toBeDefined();
          });
      });
  });
  </code></pre>
  <p>The programs finds the 3 tests but does not pass or fail them, rather skips them.
  Running the script (with windows 8.1, git bash)  returns says:</p>
  <blockquote>
  <p>Karma v0.12.1 server started atHTTP://localhost:9876/<em>karma</em>/&quot;</p>
  <p>starting Chrome Connected on Socket Chrome 31.0.1650 Executed 0 of 3</p>
  <p>(skipped 3) Error</p>
  </blockquote>
  <p>Any idea why tests that don't even need to traverse the site or look at the DOM etc can be found but can not be run?</p>