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

RFC to collocate tests in in-repo-addons #378

Closed
wants to merge 3 commits into from

Conversation

tmquinn
Copy link

@tmquinn tmquinn commented Sep 18, 2018

@luketheobscure
Copy link

I'm assuming that in-repo lazy engines would be covered under this? We might need to specify that by default the in-repo tests would use the engineResolverFor logic when setting up the resolver.

@jeanduplessis
Copy link

I would very much love to see the inclusion of having a dummy app as mentioned in the "Unresolved questions" section.

@tmquinn
Copy link
Author

tmquinn commented Sep 20, 2018

@luketheobscure Could you expand? I will make it a little clearer in the RFC that only the location of the test source code will change. The built assets will remain identical to the non-collated version.

@tmquinn
Copy link
Author

tmquinn commented Sep 20, 2018

@jeanduplessis I will try and get that RFC up as soon as possible. I'm intentionally keeping them separate as I have the code to make this RFC happen, but there is a lot of discussion that will go into the idea of separating the test output into separate bundles or having dummy apps in the in-repo-engines. Although that is certainly the end goal and the bit I am most excited to see happen!

@runspired
Copy link
Contributor

Should this RFC be in https://github.com/ember-cli/rfcs ?

@jamesarosen
Copy link

See also ember-cli/rfcs#60

@tmquinn
Copy link
Author

tmquinn commented Oct 1, 2018

Should this RFC be in https://github.com/ember-cli/rfcs ?

I heard that ember-cli/rfcs might be deprecated soon. I was going to inquire if I should still move this to ember-cli, but after a recent write up, should we just leave it here?

@rwjblue
Copy link
Member

rwjblue commented Oct 1, 2018

Should this RFC be in ember-cli/rfcs ?

tldr; no, I don't think so. #300 has details (needs some edits though 😉 @locks), but I think we would generally like to reduce confusion and use a single RFCs repo.

- use `includeTestsInHost: true` in `index.js` to indicate collocated tests
- Implement CLI flag that only runs the tests for a specified addon
- `ember test --ir-addon foo-bar`
- The flag's use would create a list of tests to run that are collocated in that in-repo-addon's test folder. The tests will still be included all in one bundle, so this is basically just running the modules that are associated with the co-located tests.
Copy link

Choose a reason for hiding this comment

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

Since all the test are included into a single bundle why do we need --ir-addon flag? Build takes a while, building several --ir tests may be annoying.

What if we provide something like "Engines" or "Bundles" dropdown in qunit interface?

@wagenet
Copy link
Member

wagenet commented Jul 23, 2022

Given the inactivity here I'm going to go ahead and close this. I apologize for the fact that this stagnated and if you would still like to try to move this forward, let me know and I'll ensure that it gets a proper review.

@wagenet wagenet closed this Jul 23, 2022
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.

8 participants