Age | Commit message (Collapse) | Author | Files | Lines |
|
Migrate the custom setup.py to a more formal setup
environment using tox, in the same way that OpenStack
configures their projects.
Adds metadata to tox.ini from the setup.py file, and breaks
out the dependencies from setup.py into requirements.txt
and test-requirements.txt.
Executes flake8 testing for pep8 coverage.
Defaults to using Python 2 for the environment.
Change-Id: Ieaea7d9f3dc227febd8fb1dc9142d478ba197a92
Signed-off-by: Leif Madsen <lmadsen@redhat.com>
Signed-off-by: zshi <zshi@redhat.com>
|
|
JIRA: DOVETAIL-50
Change-Id: I65c618ce3de78677b9e66a1c2d7f0af705e80cfb
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: DOVETAIL-151
This diff introduces an optional dovetail dockerfile based on CentOS.
It provides users to have an alternative way to execute dovetail.
It should be just a optional, so we should keep docker/Dockerfile
as official one with dockerhub's image and we do not build docker images
in CI phase for now.
Change-Id: Ia694bcd49f65ff2bc175c1da3b42fbfa19b022a1
Signed-off-by: Tomofumi Hayashi <tohayash@redhat.com>
Signed-off-by: Zenghui Shi <zshi@redhat.com>
|
|
JIRA: DOVETAIL-71
1) argument testarea is added
2) terminology "scenario" change to "testsuite"
3) related documents amended
4) all word "certification" changed to "compliance"
Change-Id: I038a9e04bf83cfdac20f0c59adb1841bf5470584
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: DOVETAIL-50
1)'proposed_tests.yml' is added, which runs as the total tests run.
The 'compliance_set.yml' will run as dovetail certification tests;
2)ipv6 test cases added accroding to 'docs/testsuites/ipv6/ipv6_all_testcases',
tc026 missed temporarily,yardstick ipv6tc026 only supports 2 installers by now
according to https://wiki.opnfv.org/display/dovetail/Dovetail+Test+Cases
3)vimops001-006 added for VIM images operation test cases
4)nfvi001-002 added for vping ssh/userdata in fucntest
5)more test cases can be added in future in proposed_tests.yml,
besides, the test cases can be adjusted in future in proposed_tests.yml
Change-Id: I8a8634583549a802f6f64fbea651e7be4efa361c
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: DOVETAIL-28
1) documents are reorganized, all dovetail tool related documents are moved to /docs/dovetailtool
2) some sections are rewritten to make it more clear
Change-Id: Ib0c23b8c1771eb6de7d6cc264c101e8e26ed3d1f
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA:DOVETAIL-28
Change-Id: I2478655d951a65a11f39e9ceba10969e56274cc3
Signed-off-by: Leo Wang <grakiss.wanglei@huawei.com>
|
|
JIRA: DOVETAIL-9
1. We are keeping the test methodology simple and easy.
We are reusing existing tests as much as we can from
IPv6 projects and Tempest API and Scenario tests, which
are run in FuncTest and Yardstick.
2. We modified "testplan.rst" to briefly describe the test plan,
i.e. current IPv6 test cases for platform compliance, which
have passed FuncTest and Yardstick test in Arno and Brahmaputra
releases. We also leave room for additional IPv6 test cases if
there are more contributions down the road
3. Original "designspecification.rst", "testprocedure.rst" and
"testspecification.rst" are not applicable any more here. The
test design, setup, and execution procedure related specification
are covered by each test case.
4. Thus "index.rst" only covers "testplan.rst" and the list of test cases.
5. Two examples of test case specification documents are provided
"ipv6.tc001.specification.rst"
"ipv6.tc026.specification.rst"
6. A complete set of current IPv6 test cases are listed in
"ipv6_all_testcases.rst". Once template is agreed, we will converted
it into specific test case document.
For more background of IPv6, and its features and technical details, please see:
https://wiki.opnfv.org/display/ipv6/IPv6+Home
http://artifacts.opnfv.org/ipv6/docs/installationprocedure/index.html
Change-Id: I7e47c73c0f02a407df278c93a3da2142b5cc86e5
Signed-off-by: Bin Hu <bh526r@att.com>
|
|
Adding the first draft of the IPv6 test suite.
This patch attempts to start the documentation according to the
proposal on https://wiki.opnfv.org/pages/viewpage.action?pageId=6827269
The text is neither complete nor accurate at this stage, this patch
is intended to establish a concrete dialog for how we structure our
test suites and reference test cases.
Change-Id: I156ddafa3e8b7630390523864490426fc742eb3a
Signed-off-by: ChristopherPrice <christopher.price@ericsson.com>
|
|
JIRA: DOVETAIL-7
Change-Id: Ic17a05ea15858f6f93f112f26b532339f5904178
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
|
|
Change-Id: I6a81e832a311096d70acabe3dba20e8736d74ea7
Signed-off-by: ChristopherPrice <christopher.price@ericsson.com>
|
|
Created the initial structure for the plugfest test plan.
* Created a base directory and document structure
* Created contributor guidelines
* Created test case template
* adjusted for: http://artifacts.opnfv.org/releng/docs/how-to-use-docs/documentation-example.html
* cp: reformatted the directories and structure to use the RST format
* (we cannot review odt format in our toolchain, so use rst)
* cp: added an index.rst structure to establish structure without numbering
* cp: will ad anothe job to include dovetail in the docs toolchain
Change-Id: I4ef997da51b3b85e391629d6e08fadf87257fc6a
|