Puma is added explicitly as it complained about not finding it.
The upgrade to Rails 5.0.1 is also related to this whole Puma business.
The format of the output has changed in a few places, so I had to add some newlines to expectations.
The most confusing one was teaspoon-jasmine/spec/javascripts/jasmine2/fixture_spec.coffee. Something must have changed in the behaviour of fixture.load that Jasmine 2 doesn't agree with it.
On this one: comparing (with toEqual) the html contents is the correct expectation (from what I can tell), as content is appended to the fixture, and therefore we can't just expect the very same object to be in fixture.el and fixtures[0] (and compared with toBe).
So this fixes the build! Some notes:
teaspoon-jasmine/spec/javascripts/jasmine2/fixture_spec.coffee. Something must have changed in the behaviour offixture.loadthat Jasmine 2 doesn't agree with it.toEqual) the html contents is the correct expectation (from what I can tell), as content is appended to the fixture, and therefore we can't just expect the very same object to be infixture.elandfixtures[0](and compared withtoBe).Now I hope we can start merging PRs, particularly https://github.com/jejacks0n/teaspoon/pull/537 which is the one that triggered my effort here :-)