hadoop/hadoop-ozone/acceptance-test
Anu Engineer 950dea86f4 HDDS-112. OzoneShell should support commands with url without scheme.
Contributed by Lokesh Jain.
2018-05-31 12:05:50 -07:00
..
dev-support/bin HDDS-40. Separating packaging of Ozone/HDDS from the main Hadoop. 2018-05-11 14:24:36 -07:00
src/test HDDS-112. OzoneShell should support commands with url without scheme. 2018-05-31 12:05:50 -07:00
README.md HDDS-40. Separating packaging of Ozone/HDDS from the main Hadoop. 2018-05-11 14:24:36 -07:00
pom.xml HDDS-40. Separating packaging of Ozone/HDDS from the main Hadoop. 2018-05-11 14:24:36 -07:00

README.md

Acceptance test suite for Ozone/Hdds

This project contains acceptance tests for ozone/hdds using docker-compose and robot framework.

Run

To run the acceptance tests, please activate the ozone-acceptance-test profile and do a full build.

mvn clean install -Pdist -Phdds
cd hadoop-ozone/acceptance-test
mvn integration-test -Phdds,ozone-acceptance-test,dist -DskipTests

Notes:

  1. You need a hadoop build in hadoop-dist/target directory.
  2. The ozone-acceptance-test could be activated with profile even if the unit tests are disabled.
  3. This method does not require the robot framework on path as jpython is used.

Development

You can also run manually the robot tests with robot cli. (See robotframework docs to install it: http://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#installation-instructions)

In the dev-support directory we have two wrapper scripts to run robot framework with local robot cli instead of calling it from maven.

It's useful during the development of the robot files as any robotframework cli arguments could be used.

  1. dev-support/bin/robot.sh is the simple wrapper. The .robot file should be used as an argument.
  2. dev-support/bin/robot-all.sh will call the robot.sh with the main acceptance test directory, which means all the acceptance tests will be executed.