All test suites are meant to be run in the test environment, not in the production environment. In test, neither asset precompiling, nor SSL enforcement is on. rake selects the testing environment correctly, but for jasmine, the wiki clearly states
RAILS_ENV=test bin/rake jasmine
Why are you trying to run jasmine in the production env?
You are right, I didnāt saw this. IMHO this article is buried to deep inside the WIKI.
I started with jasmine by naively running rake jasmine - which lead into āAssets need to be precompiled in productionā.
Whats about writing a (shorter) How-To list - and / or add these steps to the contributing.md file?
Well itās linked on the front page, you canāt make that more discoverable with the current layoutā¦
The CONTRIBUTING.md already links to the testing workflow wiki page - āWrite tests.ā is one of the four steps under āContributing to the codeā. You also canāt make that any more discoverable, if people donāt read that file, then theyāll not see anything we do there.
As for condensingā¦ you canāt condense that information down without losing details, so uh, probably not. That being said, weāre currently throwing away all the contents and re-writing them for the new project site anyway, so Iāll keep that in mind.
Good to know that this will be addressed in a re-write. So Iād like to emphasis thatās a nice concession for (new) developers to find all they need in this file, without diving to links. The most important steps should be prominent in this file.
Diving into links only for the details.