The utility for building of AlmaLinux distributions (repos, ISO images).
Go to file
Daniel Mach 81e935fe0e Fix test data, improve Makefile.
Previous test data was insufficient for proper testing.
Test compose runs and depsolving tests require precisely
set NVRs, dependencies, sub-packages, etc.
Using rpmfluff for these would be an overkill, it's better
to create RPMs directly from specs.
2015-06-25 08:02:57 -04:00
bin 4.0.1 release 2015-06-11 22:12:58 -05:00
doc update docs now devel-4-pungi is merged to master, minor spelling fixes 2015-06-07 00:28:28 +01:00
pungi pull in gather.py patches from dmach for test compose 2015-06-10 10:03:57 -05:00
share Initial code merge for Pungi 4.0. 2015-02-10 08:19:34 -05:00
tests Fix test data, improve Makefile. 2015-06-25 08:02:57 -04:00
.gitignore Fix test data, improve Makefile. 2015-06-25 08:02:57 -04:00
AUTHORS Initial changes for Pungi 4.0. 2015-02-10 06:47:16 -05:00
COPYING Initial changes for Pungi 4.0. 2015-02-10 06:47:16 -05:00
GPL Update GPL to latest version from https://www.gnu.org/licenses/gpl-2.0.txt 2015-06-25 07:50:03 -04:00
MANIFEST.in fixup setup.py and MANIFEST.in to make a useable tarball 2015-03-12 11:03:48 -05:00
Makefile Fix test data, improve Makefile. 2015-06-25 08:02:57 -04:00
README.testing Fix test data, improve Makefile. 2015-06-25 08:02:57 -04:00
TODO Initial code merge for Pungi 4.0. 2015-02-10 08:19:34 -05:00
git-changelog 3.04 release 2014-04-29 16:29:34 -05:00
pungi.spec 4.0.1 release 2015-06-11 22:12:58 -05:00
setup.py Fix test data, improve Makefile. 2015-06-25 08:02:57 -04:00

README.testing

===============
 Testing Pungi
===============


Test Data
=========
Tests require test data and not all of it is available in git.
You must create test repositories before running the tests:

 $ make test-data

Requirements: createrepo_c, rpmbuild


Unit Tests
==========
Unit tests cover functionality of Pungi python modules.
You can run all of them at once:

 $ make test

which is shortcut to:

 $ python2 setup.py test
 $ python3 setup.py test

You can alternatively run individual tests:

 $ cd tests
 $ ./<test>.py [<class>[.<test>]]


Functional Tests
================
Because compose is quite complex process and not everything is covered with
unit tests yet, the easiest way how to test if your changes did not break
anything badly is to start a compose on a relatively small and well defined
package set:

 $ cd tests
 $ ./test_compose.sh