This Code is written for and used in the CentOS Automated QA tests process. We welcome all contributions.

See the doc directory for additional information on test writing.

Pulling from upstream

git remote add upstream git@github.com:CentOS/sig-core-t_functional.git
git pull upstream master
... # RESOLVE CONFLICTS
git add . 
git commit -m 'Pulled from upstream'
git push origin master
# Additionally the following should be made
grep 'centos_ver' -R . # check if there are any file that has centos_ver
./debrand.sh

Running tests

To run these tests on your local machine (DO NOT do that if it's NOT the test machine):

./runtests.sh

To only run a specific test ( e.g. p_openssh ) :

./runtests.sh p_openssh

Checking test scripts/running all tests in a controlled environment

The easiest way of checking if tests are passing/correct is to run them on eurolinux 6,7,8 or 9 vagrant box.

VER=9
vagrant init eurolinux-vagrant/eurolinux-$VER
vagrant up
# for rsynced boxes
vagrant ssh -c "cd /vagrant; sudo /vagrant/runtests.sh"

Nearly identical processes run on our CI/CD.

Writing tests

There is a dedicated wiki page covering that. As a newcomer, you should read this document from start to finish. Questions/comments/suggestions should be voiced in the #centos-devel channel on Libera IRC, or via email on the centos-devel@centos.org mailing list.

Disabling tests

While it's a very bad idea, sometimes, during major.minor release, our scripts really find issues that are then reported upstream. For the time being, one can add tests to be skipped by our QA harness setup (validating all new installable trees)

See the skipped-tests.list file.