PulpQE / pulp-smash / 508 / 2
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: 70.276% (+0.6%) from 69.679%
508.2

push

travis-ci

Ichimonji10 
Change expected configuration file contents

Fix https://github.com/PulpQE/pulp-smash/issues/224

It's technically already possible to create test cases that target both
a Pulp server and a Pulp agent. However, there is not proper
documentation for how to do this. Create such.

The most significant change in this commit regards the contents of
configuration files. Configuration files may now have two sections.
Here's what `python -m pulp_smash` has to say about the topic:

> The configuration file should have this structure:
>
>     {
>         "pulp": {
>             "base_url": "https://pulp.example.com",
>             "auth": ["username", "password"],
>             "verify": true,
>             "version": "2.7.5",
>             "cli_transport": "local"
>         },
>         "pulp agent": {
>             "base_url": "https://pulp-agent.example.com"
>         }
>     }
>
> Each section provides information about a single Pulp-related service
> and the host on which that service is installed. The "pulp" and "pulp
> agent" sections tell about the Pulp and Pulp Agent services,
> respectively. The former is required. The latter is optional, and if
> omitted, relevant tests are skipped.

The assertion that "relevant tests are skipped" will only hold true if
individual test tests (or test modules) implement such checks. A proof
of concept showing that this can be done has been written.

If a user calls `ServerConfig.read`, does not specify which
configuration file section to read, and the configuration file has a
single section named `default`, then that section is read and a
deprecation warning is raised.

357 of 508 relevant lines covered (70.28%)

0.7 hits per line

Source Files on job 508.2