Uh oh!
There was an error while loading. Please reload this page.
Functional tests for atomicapp - #655
Conversation
cdrage
commented
Mar 30, 2016
This looks cool! 👯 good job so far! So out of curiosity, we're leaving the openshift/docker/k8s environments up to the user to decide :). Also when running the functional tests I hope that's it per provider instead of a |
concaf
commented
May 2, 2016
rtnpro
commented
May 5, 2016
@containscafeine Makes sense! However, if there's a bug in the library, the bug comes in testing as well. |
rtnpro
commented
Aug 18, 2016
@kadel@surajssd@cdrage @containscafeine Could you have a look at the PR? The functional tests for kubernetes and docker are working, however gets stuck for the openshift, provider, the mariadb pod comes up fine, but the wordpress pod just gets stuck at |
Hmm, I have to look at it closer, but OpenShift fails to start for me :-( k8s and docker OK |
| --privileged --pid=host --net=host \ | ||
| -v /:/rootfs:ro -v /var/run:/var/run:rw -v /sys:/sys -v /var/lib/docker:/var/lib/docker:rw \ | ||
| -v /var/lib/origin/openshift.local.volumes:/var/lib/origin/openshift.local.volumes \ | ||
| openshift/origin start""" |
There was a problem hiding this comment.
we shouldn't use latest image. This should be latest stable version, currently openshift/origin:v1.2.1
rtnpro
commented
Aug 29, 2016
Could you review it? |
cdrage
commented
Aug 29, 2016
#dotests |
cdrage
commented
Aug 29, 2016
Tests still seem to fail :( @rtnpro |
cdrage
commented
Aug 29, 2016
Are we able to add an ignore somehow or putting the functional tests in a different directory for testing? |
@cdrage the unittests failed because the test runners are trying to run the functional tests as well. We need to execute unittests using |
cdrage
commented
Aug 30, 2016
@rtnpro this needs to be fixed then so that travis will only run the non-functional tests, or else every PR is going to fail since it's trying to run the functional tests :) i'd advise putting the functional tests into a different folder |
rtnpro
commented
Aug 30, 2016
On Tue, Aug 30, 2016 at 7:21 PM, Charlie Drage notifications@github.com
Ratnadeep Debnath, |
coveralls
commented
Aug 31, 2016
coveralls
commented
Aug 31, 2016
cdrage
commented
Aug 31, 2016
#dotests |
1 similar comment
cdrage
commented
Aug 31, 2016
#dotests |
cdrage
commented
Sep 1, 2016
Getting this error: |
cdrage
commented
Sep 1, 2016
I'm assuming this is due to failure in Debian-based OS' ^^. Mind patching in a detection if selinux is installed and/or what OS you're running? |
| if getenforce == 'Enforcing': | ||
| subprocess.check_output('setenforce 0', shell=True) | ||
| cls._enable_selinux = True | ||
There was a problem hiding this comment.
needs to account for debian/ubuntu OS'
836125e to
d0b57edComparecoveralls
commented
Sep 6, 2016
- base test suite for generic provider - base test suite for kubernetes provider.
- openshift - kubernetes
The default value is assumed to be a directory named 'nulecule-library' adjacent to the 'atomicapp' directory.
d0b57ed to
5974a24Comparecoveralls
commented
Sep 27, 2016
in functional tests.
coveralls
commented
Sep 27, 2016
rtnpro
commented
Sep 27, 2016
@cdrage could you review it, once again? I am still not able to make py.test work with TTY enabled with |
cdrage
commented
Sep 27, 2016
@rtnpro still seems to fail upon running the tests: endless delay at that point / freezes up. |
cdrage
commented
Sep 27, 2016
Also.. weird issue.. For some reason, if I run the functional tests within the atomicapp git repo |
cdrage
commented
Sep 27, 2016
Here is the full log running |
Uh oh!
There was an error while loading. Please reload this page.