Skip to content

Create an integration test suite #17

Closed
skuro opened this Issue May 8, 2012 · 1 comment

1 participant

@skuro
Owner
skuro commented May 8, 2012

An in-container integration test should ensure that all things are correctly in place. At least the following should be tested:

  • authentication
  • CRUD on nodes and properties
  • search
@skuro skuro was assigned May 29, 2012
@skuro skuro added a commit that referenced this issue Jun 28, 2012
@skuro #17 first in-container functional test 2d9c8d1
@skuro skuro added a commit that referenced this issue Jun 28, 2012
@skuro #17 merged from trunk 5b2c37b
@skuro
Owner
skuro commented Jun 28, 2012

Strangely enough, Travis fails to start up the container in the pre-integration-test phase due to temp folder location permissions, but the build is still green..

Anyway, fix the default temp folder to use a ./target relative path

@skuro skuro added a commit that referenced this issue Jun 30, 2012
@skuro #17 longer timeouts for nrepl clients e4982aa
@skuro skuro added a commit that referenced this issue Jun 30, 2012
@skuro #17 merged from master 7a9cb60
@skuro skuro added a commit that referenced this issue Jun 30, 2012
@skuro #17 run with junit for jenkins sake 5bde057
@skuro skuro added a commit that referenced this issue Jun 30, 2012
@skuro #17 test with junit for jenkins sake fdf1bec
@skuro skuro closed this Jul 17, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.