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

Any way to avoid download assets when running tests #65

Open
arist0tl3 opened this issue May 28, 2017 · 1 comment
Open

Any way to avoid download assets when running tests #65

arist0tl3 opened this issue May 28, 2017 · 1 comment

Comments

@arist0tl3
Copy link

Hey,

just wondering if there is a way to avoid downloading the assets when running tests on something like CircleCI? We're currently caching as much as possible, but a good chunk of our tests look like:

Downloading zodiase:mdl-assets@1.3.0...   [=================      ] 72% 13.2s

Thanks in advance!

@Zodiase
Copy link
Owner

Zodiase commented May 29, 2017

I think if you are using your project dev files for testing then all the downloading is unavoidable and quite necessary (to reproduce the setup and installation process of the project). I'd assume your testing environment also have to install Meteor or other packages as well? IMO all those are essential part of the testing (when against the dev files).

The better way I think is to only test the production bundle, which includes all Meteor related stuff. So the assets package or whatever other large packages only get download once on your development machine, build and bundle the app for CI, then no more downloading needed once in the CI environment. But I think you still have to download all npm packages.

Then the ultimate solution is to have all the dependencies that otherwise require downloading ready in the test environment. For example Meteor and npm both have cache folder storing already downloaded packages to skip downloading. If you could somehow setup your testing environment to start with all the dependencies ready to be copied, then it sure can save some time in the testing process.

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

No branches or pull requests

2 participants