With the new testing framework it's possible to create FakePkg with metadata and files, so it's possible to replace binary rpm that are used just for testing simple functionality. This way it's possible to remove the number of binary files and it'll be easier to understand what the tests are doing.
Of course we cannot remove all the files inside test/binary/ because it's good test with real rpms, but a lot of tests are using small rpm created just to test a check and the sources of these rpm are not in the repository so it's hard to modify it, so any test that we can update to use FakePkg instead of binary rpm will be an improvement.
Easy
Medium
Hard
With the new testing framework it's possible to create
FakePkgwith metadata and files, so it's possible to replace binary rpm that are used just for testing simple functionality. This way it's possible to remove the number of binary files and it'll be easier to understand what the tests are doing.Of course we cannot remove all the files inside
test/binary/because it's good test with real rpms, but a lot of tests are using small rpm created just to test a check and the sources of these rpm are not in the repository so it's hard to modify it, so any test that we can update to useFakePkginstead of binary rpm will be an improvement.Easy
Medium
pkg.dirname)Hard
rpm.dsin theDockCheck.py. files, permissions and requirements. Files with RPMFILE_DOC flag)read_with_mmaptoAbstractPkg)POSTIN/POSTUNscripts)test/files/binaries?)