QA:Depcheck Test Case

From FedoraProject

Jump to: navigation, search

Contents

Description

This test is designed to ensure that a proposed package update does not introduce any dependency problems into the targetted repository (updates or updates-testing).

Setup

The test environment consists of any machine with depcheck script downloaded. When downloading packages from the fedora build system (koji), you will need to install the Package-x-generic-16.pngkoji package by typing: yum install koji

How to test

  1. Download all builds (i.e. all RPMs from a build for every build) currently present in a Koji tag you want to test. For example to list all builds currently proposed to stable Fedora 13 updates, you can run:
    koji list-tagged dist-f14-updates-pending
    

    You can download them all e.g. like this:

    koji list-tagged dist-f14-updates-pending --quiet | cut -f1 -d ' ' | while read BUILD; do koji download-build $BUILD; done
    
    Important.png
    Download all proposed packages
    It is absolutely necessary to always download all packages proposed for inclusion into some repository. If you download just some of them the test result may not be valid.
  2. Run depcheck script with the desired target repository (notice different syntax) and all the downloaded RPMs as arguments:
    depcheck f14-updates *.rpm
    
  3. Examine depcheck output. Builds listed as ACCEPTED do not break dependencies. However, builds listed as REJECTED break them.
  4. Repeat this approach for all supported architectures - i686 and x86_64. (I.e. follow this test case on both 32-bit and 64-bit Fedora).

Expected Results

  1. All updates are listed as ACCEPTED. In other words, none of the proposed updates are listed as REJECTED.