Hi all, I've noticed that fstests doesn't document what the test groups mean. I attempted to document what each group seems to symbolize, to reduce the amount of confusion for new contributors. While doing so, I noticed that there were a handful of tests that aren't in the right group. The first three patches dix that problem. The next test adds a build-time check to ensure that all groups are listed in the documentation file so that we don't lose track of things. The last patch updates ./new to use the documentation file instead of having to build group.list files. If you're going to start using this mess, you probably ought to just pull from my git trees, which are linked below. This is an extraordinary way to destroy everything. Enjoy! Comments and questions are, as always, welcome. --D fstests git tree: https://git.kernel.org/cgit/linux/kernel/git/djwong/xfstests-dev.git/log/?h=document-test-groups --- doc/group-names.txt | 136 ++++++++++++++++++++++++++++++++++++++++++++++++ include/buildgrouplist | 1 new | 24 ++++---- tests/ceph/001 | 2 - tests/ceph/002 | 2 - tests/ceph/003 | 2 - tests/xfs/491 | 2 - tests/xfs/492 | 2 - tests/xfs/493 | 2 - tests/xfs/519 | 2 - tests/xfs/520 | 2 - tests/xfs/535 | 2 - tests/xfs/536 | 2 - tools/check-groups | 33 ++++++++++++ 14 files changed, 191 insertions(+), 23 deletions(-) create mode 100644 doc/group-names.txt create mode 100755 tools/check-groups
