Skip to content

Latest commit

 

History

History
 
 

tests

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
python
python
 
 
test_data
test_data
 
 
CMakeLists.txt
CMakeLists.txt
 
 
README.rst
README.rst
 
 
fixtures.c
fixtures.c
 
 
fixtures.h
fixtures.h
 
 
run_tests.sh.in
run_tests.sh.in
 
 
test_checksum.c
test_checksum.c
 
 
test_checksum.h
test_checksum.h
 
 
test_downloader.c
test_downloader.c
 
 
test_downloader.h
test_downloader.h
 
 
test_gpg.c
test_gpg.c
 
 
test_gpg.h
test_gpg.h
 
 
test_handle.c
test_handle.c
 
 
test_handle.h
test_handle.h
 
 
test_lrmirrorlist.c
test_lrmirrorlist.c
 
 
test_lrmirrorlist.h
test_lrmirrorlist.h
 
 
test_main.c
test_main.c
 
 
test_metalink.c
test_metalink.c
 
 
test_metalink.h
test_metalink.h
 
 
test_mirrorlist.c
test_mirrorlist.c
 
 
test_mirrorlist.h
test_mirrorlist.h
 
 
test_package_downloader.c
test_package_downloader.c
 
 
test_package_downloader.h
test_package_downloader.h
 
 
test_repo_zck.c
test_repo_zck.c
 
 
test_repo_zck.h
test_repo_zck.h
 
 
test_repoconf.c
test_repoconf.c
 
 
test_repoconf.h
test_repoconf.h
 
 
test_repomd.c
test_repomd.c
 
 
test_repomd.h
test_repomd.h
 
 
test_url_substitution.c
test_url_substitution.c
 
 
test_url_substitution.h
test_url_substitution.h
 
 
test_util.c
test_util.c
 
 
test_util.h
test_util.h
 
 
test_version.c
test_version.c
 
 
test_version.h
test_version.h
 
 
testsys.c
testsys.c
 
 
testsys.h
testsys.h
 
 

README.rst

C tests

C tests uses the Check unit testing framework (http://check.sourceforge.net/).

Run (from your checkout dir):

build/tests/test_main tests/test_data/

Tip: Use Valgrind (http://valgrind.org/) with C tests:

valgrind build/tests/test_main tests/test_data/

Files of C tests

test_data/
  • Directory with testing repositories, metalink files, etc.
CMakeLists.txt
  • CMake config file
fixtures.c fixtures.h
  • Global test data (global test variable, setup and tear down function(s), ...)
testsys.c testsys.h
  • Global test configuration, expected results (constants in testsys.h) and useful functions (functions in testsys.h)
test_main.c
  • Main file
test_*.c test_*.h
  • Test suites

Python tests with Flask

Some python tests use Flask python framework (http://flask.pocoo.org/) to simulate web server. The server is started automatically during that tests.

TestCases with Flask inherit from TestCaseWithApp class.

The Flask is then set as the app to the test case by 'application' class attribute.

If you want to start server manually:

$ python python/tests/servermock/server.py

Url examples

http://127.0.0.1:5000/yum/auth_basic/static/01/repodata/repomd.xml
  • This url provides basic authentification
http://127.0.0.1:5000/yum/badgpg/static/01/repodata/repomd.xml.asc
  • This url in fact returns .../repodata/repomd.xml.asc.bad file

etc..

Modularity of tests with Flask

Flask tests are intended to be modular.

Modularity is provided by use of http://flask.pocoo.org/docs/blueprints/ Currently there is only one module (blueprint) for yum repo mocking in servermock/yum_mock.

Repos for test with Flask

Currently each module (blueprint) uses its own data (repositories, packages, ..).

E.g. for yum mocking module: servermock/yum_mock/static/

Configuration and globals for tests with Flask

Each module (blueprint) has its own configuration and globals which uses and provides to tests which use the module.

E.g. for yum mocking module: servermock/yum_mock/config.py