zhmcclient / python-zhmcclient / test-4295 / 2
79%
master: 79%

DEFAULT BRANCH: master
Ran
Files 61
Run time 4s
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: 79.957% (-0.04%) from 80.0%
test-4295.2

push

github

web-flow 
Function test: Improved conftest.py, completed User, added BaseResource (#2072)

* Function test: Improved conftest.py, completed User, added BaseResource

Details:

* Redesigned the JSON schema for the YAML test files:

  - Added support for defining setup resources at the test file level
    and at the testcase level by adding a new property 'setup'. That
    required the list of testcases to be moved under a top-level
    property 'testcases'. The setup objects are stored in a dictionary
    and can be looked up by URI.

  - Moved the definition of a HMC session from a top-level hmc_session
    property in each testcase to become definable at the test file level
    and at the testcase level, within the new 'setup' property.

  - Defined a schema definition 'value' that represents a Python
    value for method parameters, method return values, or property
    values. That fixed the issue that previously, zhmcclient
    resource and manager objects could only be represented as single
    objects but not as items in a list or dict. Also, zhmcclient
    resource and manager objects are now referenced via URI lookup
    in the dictionary resulting from the setup resources.

  - Changed the way the target object of the test is specified, to
    also use the same approach as for 'value', except that it must be
    either a resource or manager object.

  - Changed the way method parameter values and method return values
    are specified in the testcase YAML, to use the 'value' definition.

* Adjusted the test code in conftest.py to the new test file structure.

* In conftest.py, introduced a class TestcaseData in order to
  isolate the data properties pytest does not care about from other
  properties pytest does care about. Before that, it happened that
  a test property happened to use the name of a property known by
  pytest.

* In conftest.py, fixed the issue that requests_mock records only
  the last HTTP request/response pair, by maintaning our own... (continued)

9375 of 11725 relevant lines covered (79.96%)

0.8 hits per line

Source Files on job windows-latest,3.14,minimum - test-4295.2