Skip to content
This repository was archived by the owner on Jan 10, 2024. It is now read-only.

Conversation

PericlesTheo
Copy link

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
or
JASMINE_CONFIG=jasmine_legacy.yml bundle exec rails server

WDYT?

@Zeneixe
Copy link
Contributor

Zeneixe commented Sep 18, 2015

If you have better solutions, any other change that allows having different yml files would be very useful

Cheers!

@searls
Copy link
Member

searls commented Sep 19, 2015

looks good to me. doesn't seem like it really needs another test

searls added a commit that referenced this pull request Sep 19, 2015
Allow passing config yaml file name from environment
@searls searls merged commit a1a755c into testdouble:master Sep 19, 2015
@searls searls mentioned this pull request Nov 2, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants