PulpQE / pulp-smash / 1637 / 3
63%
master: 63%

DEFAULT BRANCH: master
Ran
Files 7
Run time 0s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 62.069%. Remained the same
1637.3

push

travis-ci

Ichimonji10 
Tweak with assertions in rsync test case

When executed, `PublishTwiceTestCase` will:

    1. Create a yum repository with a yum and rsync distributor.
    2. Add some content to the repository.
    3. Publish with the yum and rsync distributor.
    4. Publish with the yum and rsync distributor again.

    The second publish with the rsync distributor should be a fast-forward
    publish, as no new units were added to the repository between the first and
    second publishes.

Update the test case. In step 2, upload two RPMs, not one. In step 3,
assert that the "unit query step" processes exactly two RPMs, instead of
some vague number greater than zero. In step 4, continue to assert that
the "unit query step" processes exactly zero RPMs.

The rsync distributor uses iterators for much of its functionality,
meaning that several steps will always state that one item was
processed. In contrast, the "unit query step" doesn't use iterators,
which is why we can make assertions about the number of RPMs processed.
Uploading two RPMs instead of one makes it easier to parse the meaning
of test results in the future:

* If zero RPMs are processed, then this indicates that a fast-forward
  publish occurred.
* If two RPMs was processed, then this indicates that a full publish
  occurred.
* If one RPM was processed, then this might indicate that an iterator is
  being used for publishes, in which case the test needs to be
  redesigned.

See: https://pulp.plan.io/issues/2844

522 of 841 relevant lines covered (62.07%)

0.62 hits per line

Source Files on job 1637.3