It would be great if one could pass a custom yml file instead of the default one. Scenarios include having a separate application.js for legacy code and a current one.
If you do have a custom yml file then you would simply need to add the environment variable from the console before firing up the test from the web or otherwise.
RAILS_ENV=test JASMINE_CONFIG=jasmine_legacy.yml bundle exec rake spec:javascript
or
JASMINE_CONFIG=jasmine_legacy.yml bundle exec rails server
Hey humans,
It would be great if one could pass a custom yml file instead of the default one. Scenarios include having a separate
application.js
for legacy code and a current one.If you do have a custom yml file then you would simply need to add the environment variable from the console before firing up the test from the web or otherwise.
RAILS_ENV=test JASMINE_CONFIG=jasmine_legacy.yml bundle exec rake spec:javascript
orJASMINE_CONFIG=jasmine_legacy.yml bundle exec rails server
WDYT?