I had a little more time to look into this and I found the culprit [1] for the rave-portal-resources failures. I'm not sure what the intention of the change was but there certainly shouldn't be two return statements. Simply removing the return that was added causes the tests to pass. My guess is that these tests will need to be refactored anyway.
-Stanton [1] https://github.com/apache/rave/commit/e7e95e8867c0634da8d74af11de6e2d226e3ae6f#diff-7 On Sat, Aug 9, 2014 at 1:26 PM, Jmeas Apache <[email protected]> wrote: > Awesome, Stanton! That's really helpful. As far as I know, this is still an > issue. I'm sure running them in the browser will help me do some debugging. > > Thanks again :) > > On Saturday, August 9, 2014, Stanton Sievers <[email protected]> wrote: > > > Is this still an issue? > > > > This might be too little too late, but you can always run "mvn > jasmine:bdd" > > to run the specs through the browser, following the instructions in the > > terminal. Usually this entails simply going to "localhost:8234" where > you > > can run individual tests, see results, debug with dev tools, etc.. > > > > I hope that helps! > > > > -Stanton > > > > > > On Tue, Jul 15, 2014 at 2:12 PM, Jmeas Apache <[email protected] > > <javascript:;>> > > wrote: > > > > > The Angular branch's unit tests haven't been working since Matt's > rebase. > > > > > > I'm trying to figure out how to get just the output from the tests. > When > > I > > > run `mvn test` i get a lot of maven output, ultimately leading to the > > > failure, but I can't isolate what exactly is failing. Passing the -e > flag > > > didn't seem to help much. > > > > > > I also tried opening the SpecRunner (both as a file, and serving up the > > > directory at 127.0.0.1) and it wouldn't run in either situation. > > > > > > Is there a way to run the spec runner in a browser, or to otherwise get > > the > > > output of just Jasmine? > > > > > >
