ceph/qa
Casey Bodley c52cbe212f
Merge pull request #34253 from cbodley/wip-qa-rgw-too-many-shards
qa/rgw: remove 1999-shard tests from rgw/verify

Reviewed-by: Ali Maredia <amaredia@redhat.com>
2020-03-30 10:06:11 -04:00
..
archs
btrfs
cephfs
client
clusters
config
crontab
debug
distros qa/distros: add SLE-15-SP2 2020-03-27 08:17:13 +01:00
erasure-code
libceph
machine_types
mds
mon/bootstrap
msgr
nightlies
objectstore
objectstore_cephfs
overrides qa/short_pg_log: pass osd_pg_log_trim_min = 0 to exercise short pg logs 2020-03-13 08:49:32 +08:00
packages
qa_scripts
rbd
releases
rgw_bucket_sharding qa/rgw: remove 1999-shard tests from rgw/verify 2020-03-27 17:43:12 -04:00
rgw_frontend
rgw_pool_type
standalone Merge PR #34126 into master 2020-03-23 13:55:16 -05:00
suites Merge pull request #33910 from xiexingguo/wip-44532-2 2020-03-26 08:10:22 +08:00
tasks Merge PR #34248 into master 2020-03-30 08:24:59 -05:00
timezone
workunits qa/workunits/cephadm: create lvs before calling cephadm 2020-03-24 16:37:27 +01:00
.gitignore
CMakeLists.txt cmake: add import-tasks to run-tox-qa test 2020-03-27 14:54:37 +08:00
Makefile
README
find-used-ports.sh
loopall.sh
mypy.ini
run-standalone.sh
run_xfstests-obsolete.sh
run_xfstests.sh
run_xfstests_qemu.sh
runallonce.sh
runoncfuse.sh
runonkclient.sh
setup-chroot.sh
test_import.py qa: Add a tox env that can test importing files 2020-03-26 16:16:31 +08:00
tox.ini qa: Add a tox env that can test importing files 2020-03-26 16:16:31 +08:00
valgrind.supp

README

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