Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Passing defaultOptions to testem to prevent the cwd and config_dir set in testem.js from being overridden by ember-cli #7728

Merged
merged 1 commit into from Apr 2, 2018

Conversation

arthirm
Copy link

@arthirm arthirm commented Apr 2, 2018

When ember-cli invokes testem it provides defaultOptions for testem to use as a fallback option. But currently, the fallback option from ember-cli is used as progOptions in testem. And since progOptions has higher priority than fileOptions, the cwd being set in the testem.js file of an ember app is being overridden by ember-cli's fallbackOption.

Solution is to add defaultOptions as a sibling to progOptions and fileOptions in testem. And ember-cli can set defaultOptions invoke testem.

Related work in testem is in the below PR.
testem/testem#1219

@stefanpenner stefanpenner merged commit dfd1531 into ember-cli:master Apr 2, 2018
arthirm pushed a commit to arthirm/ember-cli that referenced this pull request Apr 3, 2018
Passing defaultOptions to testem to prevent the cwd and config_dir set in testem.js from being overridden by ember-cli
stefanpenner added a commit that referenced this pull request Apr 3, 2018
Merge pull request #7728 from arthirm/testem-bug-fix
kellyselden pushed a commit to kellyselden/ember-cli that referenced this pull request Apr 6, 2018
Passing defaultOptions to testem to prevent the cwd and config_dir set in testem.js from being overridden by ember-cli
@Turbo87
Copy link
Member

Turbo87 commented Apr 11, 2018

It appears that this patch has broken ember-exam ... 😭

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants