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

Improve CI tests speed: do not setup webserver and un-used packages in Unit tests #6312

Open
mattab opened this issue Sep 26, 2014 · 2 comments
Labels
c: Tests & QA For issues related to automated tests or making it easier to QA & test issues. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.

Comments

@mattab
Copy link
Member

mattab commented Sep 26, 2014

Currently when running unit tests we setup the full webserver and python package and others that are not required for the job of running the unit tests. The goal of this issue is to make this Unit tests CI job faster by skipping some initialisation in the travis.yml and scripts.

Refs #5940

@mattab mattab added the Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change. label Sep 26, 2014
@mattab mattab added this to the Short term milestone Sep 26, 2014
@mattab mattab added the c: Tests & QA For issues related to automated tests or making it easier to QA & test issues. label Oct 10, 2014
@mattab mattab modified the milestones: Mid term, Short term Dec 1, 2014
@mattab
Copy link
Member Author

mattab commented Mar 3, 2015

This also applies to Angular tests, JavascriptTests. It would free the CI jobs queue faster not to do those extra mysql + python downloads!

@mattab
Copy link
Member Author

mattab commented Mar 26, 2015

This can now be done easier with new settings from #7530

Follows up #6412

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: Tests & QA For issues related to automated tests or making it easier to QA & test issues. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Projects
None yet
Development

No branches or pull requests

1 participant