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

DEFAULT BRANCH: master
Ran
Files 6
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: 75.429%. Remained the same
202.3

push

travis-ci

Ichimonji10 
Update content applicability tests

Update tests in module
`pulp_smash.tests.platform.api_v2.test_content_applicability`. The module
docstring describes the new state of affairs:

> When a user asks Pulp to regenerate content applicability, Pulp responds with
> a call report and starts executing tasks in series. Starting with Pulp 2.8, it
> is possible for a user to explicitly request that Pulp execute tasks in
> parallel instead. This functionality is only available for certain API calls,
> and when this is done, Pulp returns a group call report instead of a regular
> call report.  (See :data:`pulp_smash.constants.CALL_REPORT_KEYS` and
> :data:`pulp_smash.constants.GROUP_CALL_REPORT_KEYS`.) :class:`SeriesTestCase`
> and :class:`ParallelTestCase` test these two use cases, respectively.

Test results before this commit:

    =========  ==========  ===================
    Pulp Ver.  Num. Tests  Test Suite Results
    =========  ==========  ===================
    2.7        4           OK
    dev (2.8)  4           FAILED (failures=1)
    =========  ==========  ===================

Test results after this commit:

    =========  ==========  ==================
    Pulp Ver.  Num. Tests  Test Suite Results
    =========  ==========  ==================
    2.7        7           OK (skipped=2)
    dev (2.8)  7           OK
    =========  ==========  ==================

Test results generated with:

    PULP_SMASH_CONFIG_FILE=$PS_CONFIG python -m unittest2 \
    pulp_smash.tests.platform.api_v2.test_content_applicability

264 of 350 relevant lines covered (75.43%)

0.75 hits per line

Source Files on job 202.3