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

Iron out docker tests #12

Open
secynic opened this issue Oct 14, 2016 · 2 comments
Open

Iron out docker tests #12

secynic opened this issue Oct 14, 2016 · 2 comments
Assignees
Milestone

Comments

@secynic
Copy link
Owner

secynic commented Oct 14, 2016

Docker tests are experimental, and run via the Travis tests for Python 2.7. What is needed:

  • More OS types/versions tested
  • Better tests (currently just makes sure that the rules/config are created correctly)
  • Re-evaluate how Travis handles the docker tests
  • Can I move the Python nosetests/coveralls to docker too?
@secynic secynic added this to the 0.2.0 milestone Oct 14, 2016
@secynic secynic self-assigned this Oct 14, 2016
@secynic
Copy link
Owner Author

secynic commented Oct 14, 2016

Writing tests for selinux and apparmor further proves the need to move nosetests/coveralls to different OS containers. I don't see this working with Travis/Ubuntu.

@secynic
Copy link
Owner Author

secynic commented Oct 15, 2016

After some dumb filesystem assumptions on my end, I got nosetests/coveralls transferred to docker (dev branch). After docker is finished, the .coverage file is copied back to the Travis host (this is to remove the need for managing Coveralls API token(s)).

I now need to optimize this process, and create different OS tests for each Travis Python version tested, reducing any duplication for the sake of overall test speed.

I also need to configure what tests get run based on the OS tested. This is to get around unique conflicts like AppArmor vs SELinux, where only one will exist.

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

No branches or pull requests

1 participant