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

Travis #47

Open
mottosso opened this issue Feb 27, 2016 · 0 comments
Open

Travis #47

mottosso opened this issue Feb 27, 2016 · 0 comments
Labels

Comments

@mottosso
Copy link
Member

Goal

Automate tests.

Implementation

Setup continuous integration on Travis with Docker.

  1. Tests are located in repository, tests.py
  2. Repository is cloned on Travis
  3. Docker downloads and runs Centos with Maya, once per version, 2013-2016
  4. Per run, trigger tests.py

Example

$ docker run --rm -ti -v $(pwd):/root mottosso/maya:2013sp1 mayapy -c "from maya import standalone, cmds;standalone.initialize();cmds.playblast = lambda *args, **kwargs: None;import nose;nose.run()"

cmds.playblast is mocked, due to platform not having access to graphical hardware. Because of that, tests cannot actually trigger a playblast. But it doesn't matter, we aren't able to validate outputted images anyway by anything other than by eye.

What could happen, is that we have 90% of the tests run headless on Travis, and a separate, optional test_graphics.py that runs locally.

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

No branches or pull requests

1 participant