PulpQE / pulp-smash / 40
89%
master: 63%

LAST BUILD BRANCH: 5873
DEFAULT BRANCH: master
Ran
Jobs 4
Files 1
Run time 23s
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
40

push

travis-ci

Ichimonji10 
Split tests into sections

Fix #11:

> All tests currently reside in `pulp_smash/tests/`. This works, but it doesn't
> scale well. How can a user find the kind of test they're looking for?

To major options were discussed: splitting tests based primarily on the
transport mechanism or splitting based primarily on the plugin targeted. The
former leads to a layout like this:

    pulp_smash/tests/
    ├── api_v2
    │   ├── platform
    │   │   └── …
    │   ├── iso
    │   │   └── …
    │   └── rpm
    │       └── …
    └── cli
        ├── platform
        │   └── …
        ├── iso
        │   └── …
        └── rpm
            └── …

The latter leads to a layout like this:

    pulp_smash/tests/
    ├── platform
    │   ├── api_v2
    │   │   └── …
    │   └── cli
    │       └── …
    ├── iso
    │   ├── api_v2
    │   │   └── …
    │   └── cli
    │       └── …
    └── rpm
        ├── api_v2
        │   └── …
        └── cli
            └── …

Implement the latter layout for the following reasons:

* This layout bears a rough resemblance to Pulp Automation's layout, which is
  split in to `general_tests`, `consumer_agent_tests`, `regression_tests` and
  `nodes`. Similarity should ease the process of porting tests, and if the
  layout works over there, why change things?
* A user may not have a full set of test systems available, and in that case,
  the ability to easily run tests that target only specific plug-ins may be
  desirable. For example, if a user only has a Pulp system, they may wish to run
  only the "platform" tests.
* This approach may be the most useful to developers. For example, if a
  developer is fiddling with the Puppet plug-in, this approach makes it easy to
  run some or all of the tests for that plug-in.

There are some downsides to this approach:

* This layout may pose problems if, say, API v2 is phased out in favor of API v3
  and a user wishes to only run the v3 tests.
* Selecting tests based on their location in a filesystem... (continued)

81 of 91 relevant lines covered (89.01%)

3.56 hits per line

Jobs
ID Job ID Ran Files Coverage
1 40.1 0
89.01
 Travis Job 40.1
2 40.2 0
89.01
 Travis Job 40.2
3 40.3 0
89.01
 Travis Job 40.3
4 40.4 0
89.01
 Travis Job 40.4
Source Files on build 40
Detailed source file information is not available for this build.