ceph/qa
Varsha Rao af3b925dfd qa/tasks/cephfs: Add tests for nfs exports
Signed-off-by: Varsha Rao <varao@redhat.com>
2020-05-29 14:56:34 +05:30
..
archs
btrfs
cephfs
client
clusters
config
crontab Merge pull request #32829 from Devp00l/wip-43765 2020-05-14 13:45:16 -07:00
debug
distros Revert "qa/tests: replaced ubuntu_latest.yaml with ubuntu 20.04" 2020-05-18 21:55:25 +00:00
erasure-code
libceph
machine_types qa/tests: reduce number of jobs for rados to 309 2020-05-12 15:40:01 -07:00
mds
mon/bootstrap
msgr
nightlies
objectstore
objectstore_cephfs
overrides
packages
qa_scripts
rbd
releases
rgw_bucket_sharding
rgw_frontend
rgw_pool_type
standalone qa/standalone/scrub/osd-scrub-snaps.sh: fix grep pattern 2020-05-28 22:41:38 +00:00
suites qa/cephfs: Add tests for nfs 2020-05-29 14:47:32 +05:30
tasks qa/tasks/cephfs: Add tests for nfs exports 2020-05-29 14:56:34 +05:30
timezone
workunits Merge pull request #35033 from badone/wip-test-the-right-rocksdb-version 2020-05-27 21:58:16 +08:00
.gitignore
CMakeLists.txt
find-used-ports.sh
loopall.sh
Makefile
mypy.ini
README
run_xfstests_qemu.sh
run_xfstests-obsolete.sh
run_xfstests.sh
run-standalone.sh
runallonce.sh
runoncfuse.sh
runonkclient.sh
setup-chroot.sh
test_import.py
tox.ini qa/cephadm: Add local registry mirror 2020-05-26 17:38:39 +02:00
valgrind.supp qa/valgrind.supp: less specific when suppressing issues/22052 2020-05-25 00:02:46 +08:00

ceph-qa-suite
-------------

clusters/    - some predefined cluster layouts
suites/      - set suite

The suites directory has a hierarchical collection of tests.  This can be
freeform, but generally follows the convention of

  suites/<test suite name>/<test group>/...

A test is described by a yaml fragment.

A test can exist as a single .yaml file in the directory tree.  For example:

 suites/foo/one.yaml
 suites/foo/two.yaml

is a simple group of two tests.

A directory with a magic '+' file represents a test that combines all
other items in the directory into a single yaml fragment.  For example:

 suites/foo/bar/+
 suites/foo/bar/a.yaml
 suites/foo/bar/b.yaml
 suites/foo/bar/c.yaml

is a single test consisting of a + b + c.

A directory with a magic '%' file represents a test matrix formed from
all other items in the directory.  For example,

 suites/baz/%
 suites/baz/a.yaml
 suites/baz/b/b1.yaml
 suites/baz/b/b2.yaml
 suites/baz/c.yaml
 suites/baz/d/d1.yaml
 suites/baz/d/d2.yaml

is a 4-dimensional test matrix.  Two dimensions (a, c) are trivial (1
item), so this is really 2x2 = 4 tests, which are

  a + b1 + c + d1
  a + b1 + c + d2
  a + b2 + c + d1
  a + b2 + c + d2

A directory with a magic '$' file represents a test where one of the other
items is chosen randomly. For example,

suites/foo/$
suites/foo/a.yaml
suites/foo/b.yaml
suites/foo/c.yaml

is a single test.  It will be either a.yaml, b.yaml or c.yaml.  This can be
used in conjunction with the '%' file in other directories to run a series of
tests without causing an unwanted increase in the total number of jobs run.

Symlinks are okay.

The teuthology code can be found in https://github.com/ceph/teuthology.git