slipstream / slipstreamtests Goto Github PK

0.0 0.0 0.0 93 KB

SlipStream functional and system tests.

Clojure 95.29% Makefile 4.71%

slipstreamtests's Introduction

SlipStream is now deprecated -> replaced by https://github.com/nuvla

SlipStream

Developed by SixSq, SlipStream is a multi-cloud application management platform. See the SlipStream product page for more detailed information.

Release Notes

The release notes are available from the main SlipStream documentation website. Stable releases are those that have been validated and are supported. Candidate releases are (usually) the result of each development iteration and may or may not be stable. These can be used but are not supported.

Getting started

See the Developer Guide on the main SlipStream documentation website. This contains the full, supported build procedure for SlipStream, including the required build tools and dependencies.

License and copyright

The code in the public repositories is licensed under the Apache license.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

slipstreamtests's People

Contributors

Watchers

slipstreamtests's Issues

update tests after changes in the SlipStreamClientAPI

At the moment Enterprise_deploy on CI fails due to

java.io.FileNotFoundException: Could not locate sixsq/slipstream/client/api/lib/run__init.class or sixsq/slipstream/client/api/lib/run.clj on classpath.

tests use default connector for some components in applications

The two tests that deploy applications set the cloud connector for only one component of the application. The other components of the application use the default connector configured by the user. If the default isn't the same as the connector under test, then this will be a multi-cloud deployment that implicitly depends on the correct configuration of both connectors and the correct operation of both clouds.

This complicates the debugging of failures and make it more difficult to isolate problems to the software or a particular cloud provider. All of the application tests should use a single cloud for the deployment, unless a specific multi-cloud test is added.

add insecure parameter to func-test task

no tests run if --connectors is not provided

There are connector independent tests. It should be possible to run them w/o specifying --connectors parameter.

update deployment tests after changes in Clojure client API

Tests to fix

sixsq.slipstream.run-comp-test
sixsq.slipstream.run-app-test
sixsq.slipstream.run-app-scale-test

fix authn failures in the deployment functional tests

The main authn test succeeds, but the authn in the deployment functional tests fails. Works when launching manually from my dev machine.

: 2018-03-13T04:12:16Z : Calling: make test-run-comp TESTOPTS= --username test --connectors exoscale-ch-gva --endpoint https://159.100.251.191 --results-dir /root/test-results --comp-uri examples/tutorials/service-testing/apache --password xxx -i
cd clojure && \
	boot --no-colors func-test -n sixsq.slipstream.run-comp-test --username test --connectors exoscale-ch-gva --endpoint https://159.100.251.191 --results-dir /root/test-results --comp-uri examples/tutorials/service-testing/apache --password xxx -i

log4j:WARN No appenders could be found for logger (io.netty.util.internal.logging.InternalLoggerFactory).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

Testing sixsq.slipstream.run-comp-test

FAIL in (test-component-deploy-terminate) (run_comp_test.clj:56)
Authenticate.
expected: (authn/authenticated? client-sync)
  actual: (not
           (authn/authenticated?
            #object[sixsq.slipstream.client.sync.cimi-sync 0x77264574 "sixsq.slipstream.client.sync.cimi-sync@77264574"]))

FAIL in (test-component-deploy-terminate) (run_comp_test.clj:57)
Authenticate.
expected: 200
  actual: nil
    diff: - 200
          +
ERROR in (test-component-deploy-terminate) (core.clj:4739)
Uncaught exception, not in assertion.
expected: nil
  actual: clojure.lang.ExceptionInfo: Cookie or user credentials are required.
 at clojure.core$ex_info.invokeStatic (core.clj:4739)

getting status of clouds from nagios fails

Stop using SS HttpClient with username/password.

Traceback (most recent call last):
  File "./ss-tester.py", line 329, in <module>
    connectors_to_test = _get_connectors_to_test(SS_SERVICES_IN_NAGIOS)
  File "./ss-tester.py", line 211, in _get_connectors_to_test
    monitored_failing = _failing_monitored_connectors(monitored_ss)
  File "./ss-tester.py", line 192, in _failing_monitored_connectors
    status = _get_monitoring_status()
  File "./ss-tester.py", line 172, in _get_monitoring_status
    h = HttpClient(username=nagios_user, password=nagios_pass)
TypeError: __init__() got an unexpected keyword argument 'username'

func-test task bails out on the first failed test and doesn't run func-test-post task

This is because adzerk.boot-test/test task is used, for which this is the only unconditional behaviour. There is adzerk.boot-test/run-tests task that doesn't fail even if the test(s) it ran failed.

Solution: allow to select between the two behaviours by

use both adzerk.boot-test/run-tests and adzerk.boot-test/test tasks, with run-tests as default;
add --fail option to func-test task to let to switch to test task and fail.