hadoop/hadoop-ozone/dist/src/main/smoketest
2019-04-29 07:46:01 -07:00
..
auditparser HDDS-1255. Refactor ozone acceptance test to allow run in secure mode 2019-04-01 17:04:28 +02:00
basic HDDS-1216. Change name of ozoneManager service in docker compose files to om. 2019-03-06 15:18:39 +01:00
ozonefs HDDS-1216. Change name of ozoneManager service in docker compose files to om. 2019-03-06 15:18:39 +01:00
s3 HDDS-1255. Refactor ozone acceptance test to allow run in secure mode 2019-04-01 17:04:28 +02:00
security HDDS-1255. Refactor ozone acceptance test to allow run in secure mode 2019-04-01 17:04:28 +02:00
__init__.robot HDDS-1255. Refactor ozone acceptance test to allow run in secure mode 2019-04-01 17:04:28 +02:00
.env HDDS-223. Create acceptance test for using datanode plugin. Contributed by Sandeep Nemuri. 2018-11-15 15:18:07 +01:00
commonlib.robot HDDS-1472. Add retry to kinit command in smoketests. Contributed by Ajay Kumar. (#778) 2019-04-29 07:46:01 -07:00
createbucketenv.robot HDDS-1333. OzoneFileSystem can't work with spark/hadoop2.7 because incompatible security classes. Contributed by Elek, Marton. (#653) 2019-04-05 09:29:21 -07:00
env-compose.robot HDDS-1333. OzoneFileSystem can't work with spark/hadoop2.7 because incompatible security classes. Contributed by Elek, Marton. (#653) 2019-04-05 09:29:21 -07:00
README.md HDDS-447. Separate ozone-dist and hadoop-dist projects with real classpath separation. Contributed by Elek Marton. 2018-09-24 10:10:11 -07:00
test.sh HDDS-1255. Refactor ozone acceptance test to allow run in secure mode 2019-04-01 17:04:28 +02:00

Ozone Acceptance Tests

This directory contains a robotframework based test suite for Ozone to make it easier to check the current state of the package.

You can run in in any environment after installing

cd $DIRECTORY_OF_OZONE
robot smoketest/basic

The argument of the robot could be any robot file or directory.

The current configuration in the robot files (hostnames, ports) are adjusted for the docker-based setup but you can easily modify it for any environment.

The ./test.sh in this directory can start multiple type of clusters (ozone standalone or ozone + hdfs) and execute the test framework with all of the clusters.