#151: Need owner to define basic container smoke testing requirements
---------------------+--------------------------
Reporter: acarter | Owner: maxamillion
Type: task | Status: accepted
Priority: normal | Milestone: Future
Component: --- | Resolution:
Keywords: meeting |
---------------------+--------------------------
Comment (by tflink):
I can't speak to what other folks are planning to do in terms of testing
around docker and layered images but the functionality planned from a
Taskotron POV for the F25 timeframe is:
* ability to trigger on layered image build completion
* dist-git repos to store tests to be run automatically on individual
layered images
* ability to retrieve a layered image under test
* ability to run shell commands (stepping stone to whatever tests are
written for the layered image)
* utilities to get data into correct formats for centralized reporting
There are no plans for a "docker image testing framework" right now
because it doesn't seem to be really wanted or needed.
The only "universal" check that we're considering at the moment is running
[[http://developers.redhat.com/blog/2016/05/02/introducing-atomic-scan-
container-vulnerability-detection/|Atomic Scan]] on every image but there
are no concrete plans for if/when that would be complete.
We're also set up to run [[http://docker-
autotest.readthedocs.io/en/latest/index.html|docker-autotest]] but there
hasn't been discussion around when to actually run that. At the moment,
our dev instance is set to run the suite on every completed build of
docker in koji.
My understanding of the situation extends to the following (please
correct me if I'm wrong on any of these points):
* there are not really any good universal checks to run on all layered
images outside potential for atomic scan listed above
* there are no good, existing, practical frameworks for testing docker
images
* one of the few requirements that I've gotten for this is to not
restrict test writing to a single language or framework
* image creators will be responsible for the tests which run on new
images
* there are no concrete requirements for how/if new layered images
should be tested at this time
I don't think this will answer all of the questions here but it should
provide some useful related information
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/151#comment:7>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
