-
-
Notifications
You must be signed in to change notification settings - Fork 54
Run tests from pods #44
Comments
@keithkelly this has been brought up in emberjs/rfcs#124 Might want to look at what they're talking about and add your reaction or ideas as this is a part of the proposal. |
tests in pods, and then being able to run only tests from a pod or two, seems like a great idea. |
Tests in "pods" makes sense, and there really isn't anything preventing us from doing something like that right now: However, with the advent of better module selection inside of Qunit itself I'm not sure how much sense this makes? Maybe for CI mode? /cc @trentmwillis |
This is related to the module normalization and testing unification RFC's. When those two RFC's are implemented this should "just work". |
I personally dislike co-locating test code and app code. That said, I think after the module RFC lands, this could make more sense. Some questions to consider:
|
wherever they make sense contextually
sibling to engines/apps
I would imagine pods could contain a test dir, that could contain the specific linting rules, Although yes this does seem bad. |
@trentmwillis i believe the value here would be for unit level test, tests that are highly contextual. Atleast that is the thought. |
This is related to ember-cli/ember-cli#4461 |
We are working on closing the ember-cli/rfcs repo in favor of using a single central RFC's repo for everything. This was laid out in https://emberjs.github.io/rfcs/0300-rfc-process-update.html. Sorry for the troubles, but would you mind reviewing to see if this is still something we need, and if so migrating this over to emberjs/rfcs? |
In the spirit of independent components and the better organization of pods, I think that being able to save and run tests frompods will help to keep the file structure more organized.
The text was updated successfully, but these errors were encountered: