Test the ansible validations
Bug #1594785 reported by
Tomas Sedovic
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Gael Chamoulaud |
Bug Description
While a full validation testing would require a complete running deployment, we ought to at least unit test the custom Python modules we're using:
http://
affects: | tripleo-validations → tripleo |
tags: | added: validations |
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in tripleo: | |
assignee: | Katerina Pilatova (kpilatov) → Martin André (mandre) |
Changed in tripleo: | |
assignee: | Katerina Pilatova (kpilatov) → Gael Chamoulaud (gael-chamoulaud) |
Changed in tripleo: | |
milestone: | none → stein-3 |
Changed in tripleo: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Since the validations we're imorting have all been manually tested and the important work is usually outside of the main function, we could just do simple unit tests before doing the heavier checking described in the articles above.
We should write code that provides the necessary machinery (install ansible in the test virtual environment, etc.) and then base all the unit test patches on top of that to avoid merge conflicts.
Here's a patch that adds a unit test and so we could just split that part off:
https:/ /review. openstack. org/#/c/ 341586/