diff options
author | stark, steven <steven.stark@att.com> | 2019-01-28 14:59:01 -0800 |
---|---|---|
committer | stark, steven <steven.stark@att.com> | 2019-01-29 08:03:41 -0800 |
commit | 48a07b6942d3956666d30947372653feb702fdae (patch) | |
tree | 5a5fc3135f2703ad19543b78e661ea954e98bb33 /README.rst | |
parent | 43130f8b173d9053ad4f56f264376851d3fb890c (diff) |
[VVP] stand alone tool, script updates
1) Validation script updates:
Various bug fixes and script enhancements
New tests for:
R-18683
R-94669
R-304011
R-01455
R-86476
R-708564
R-85734
R-18683
R-94669
R-304011
R-01455
R-86476
R-86476
R-589037
Removed tests for:
R-75202
R-62954
R-22441
R-49177
R-16576
R-86237
R-44491
R-70757
R-01896
R-26124
2) Stand Alone tool introduced
3) Added optional "categories" capability
Change-Id: I193cd5c267750791d97b350e91fc36faa72d8d5f
Issue-ID: VVP-143
Signed-off-by: stark, steven <steven.stark@att.com>
Diffstat (limited to 'README.rst')
-rw-r--r-- | README.rst | 22 |
1 files changed, 11 insertions, 11 deletions
@@ -1,6 +1,6 @@ .. This work is licensed under a Creative Commons Attribution 4.0 International License. .. http://creativecommons.org/licenses/by/4.0 -.. Copyright 2018 AT&T Intellectual Property. All rights reserved. +.. Copyright 2019 AT&T Intellectual Property. All rights reserved. Manual Heat Template Validation =============================== @@ -239,8 +239,8 @@ such as the ``yaml_file``, the parameter the test was checking, etc... If the assert statement fails, the failure is collected by ``pytest``, and the associated requirements and error_message are included in the final report. -Optional: Pytest Markers and Validation Profiles -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Optional: Pytest Markers and Validation Categories +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The VVP test suite has the concept of a ``base`` test. These are used as sanity tests and are executed before the other tests, and if they fail the @@ -255,14 +255,14 @@ test like this: @validates("R-123456") def test_my_new_requirement(): -The VVP test suite also has the concept of a ``validation profile`` to -define what set of tests to execute. The way it works is by using ``pytest`` -markers. +The VVP test suite also has the concept of a ``category`` to +define what additional set of optional tests to execute. The way it works +is by using ``categories`` decorator. -By default, all ``base`` tests and non-marked tests are executed. If you want -an additional profile to run, pass the command line argument: +By default, all ``base`` tests and tests with no category are executed. +If you want an additional category to run, pass the command line argument: -``--validation-profile=<my_validation_profile>`` +``--category=<category>`` This will execute all ``base`` tests, non-marked tests, and tests marked like the following: @@ -271,12 +271,12 @@ and tests marked like the following: import pytest - @pytest.mark.<my_validation_profile> # this is an additional pytest marker + @categories("<category>") # substitue <category> with the category name @validates("R-123456") def test_my_new_requirement(): This should be used sparingly, and in practice consider reviewing a requirement -with the VNF Requirements team before adding a test to a validation profile. +with the VNF Requirements team before adding a test to a category. Self-Test Suite ~~~~~~~~~~~~~~~ |