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

Add basic implementation of new ember-qunit API. #286

Merged
merged 8 commits into from Oct 17, 2017
Merged

Conversation

rwjblue
Copy link
Member

@rwjblue rwjblue commented Oct 17, 2017

  • Add basic implementation of new ember-qunit API proposed in Add new QUnit testing API. rfcs#232.
  • Move legacy testing system into legacy-2-x subfolder.
  • Update to ember-test-helpers@0.7.0-beta.7.

@rwjblue rwjblue requested a review from Turbo87 October 17, 2017 19:03
PR is submitted to fix the plugin, once merged and released we can drop
this back down.
The new API relies on the the public API added for `Ember.getOwner` /
`Ember.setOwner`.
export { default as moduleFor } from './legacy-2-x/module-for';
export {
default as moduleForComponent,
} from './legacy-2-x/module-for-component';
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this looks like we might want the 100 chars/line here too

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, done in a later commit.

@@ -9,7 +11,7 @@ export { loadTests } from './test-loader';
import { loadTests } from './test-loader';
import Ember from 'ember';
import QUnit from 'qunit';
import { QUnitAdapter } from 'ember-qunit';
import QUnitAdapter from './adapter';
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how did that ever work?! 🤔

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NO CLUE!?!?!?

teardownContext,
setupRenderingContext,
teardownRenderingContext,
} from 'ember-test-helpers';
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

duplicate import?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, no. The other one is an export { .... } from which does not bring the exported things into the current scope.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh, right...

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

Successfully merging this pull request may close these issues.

None yet

2 participants