hadoop/hadoop-ozone/dist/src/main/smoketest
2019-06-12 06:51:34 -07:00
..
auditparser HDDS-1631. Fix auditparser smoketests (#892) 2019-06-04 01:30:43 -05:00
basic HDDS-1545. Cli to add,remove,get and delete acls for Ozone objects. Contributed by Ajay Kumar. (#920) 2019-06-12 06:51:34 -07:00
ozonefs HDDS-1424. Support multi-container robot test execution 2019-05-07 17:48:10 +02:00
s3 HDDS-1255. Refactor ozone acceptance test to allow run in secure mode 2019-04-01 17:04:28 +02:00
security HDDS-1545. Cli to add,remove,get and delete acls for Ozone objects. Contributed by Ajay Kumar. (#920) 2019-06-12 06:51:34 -07: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
createmrenv.robot HDDS-1607. Create smoketest for non-secure mapreduce example (#869) 2019-06-04 01:18:02 -05: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
kinit.robot HDDS-1424. Support multi-container robot test execution 2019-05-07 17:48:10 +02:00
mapreduce.robot HDDS-1607. Create smoketest for non-secure mapreduce example (#869) 2019-06-04 01:18:02 -05:00
README.md HDDS-1424. Support multi-container robot test execution 2019-05-07 17:48:10 +02:00
test.sh HDDS-1628. Fix the execution and return code of smoketest executor shell script 2019-06-05 14:04:17 +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.

Run tests in docker environment

In the ./compose folder there are additional test scripts to make it easy to run all tests or run a specific test in a docker environment.

Test one environment

Go to the compose directory and execute the test.sh directly from there:

cd compose/ozone
./test.sh

The results will be saved to the compose/ozone/results

Run all the tests

cd compose
./test-all.sh

The results will be combined to the compose/results folder.

Run one specific test case

Start the compose environment and execute test:

cd compose/ozone
docker-compose up -d
#wait....
../test-single.sh scm basic/basic.robot