summaryrefslogtreecommitdiffstats
path: root/docs
AgeCommit message (Collapse)AuthorFilesLines
2017-02-07bugfix of dovetail tool userguide documentMatthewLi1-0/+1
Change-Id: I33eea93ca0db018a5f79041152516fa48b94ba46 Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2017-01-19dovetail tool userguide documentMatthewLi5-156/+192
JIRA: DOVETAIL-182 Change-Id: Icbfa347dda3840520484d10b9d539da9c8f1d31c Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2017-01-17dovetail tool: change to git repo then pbr.version can be get inside dockerMatthewLi1-1/+1
JIRA: DOVETAIL-184 Change-Id: I6d466dc34de027faab1aa74f66cc6c8e453111d1 Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2017-01-16dovetail tool: bugfix for pip installMatthewLi1-3/+3
JIRA: DOVETAIL-183 1)pip install [options] [-e] <local project path> ... pip install [options] <archive url/path> ... 2)vim added in Dockerfile, which is convinience for offline usage Change-Id: I986dc7cd3e872cf026d2e69f7298028a6cbfe9a6 Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2017-01-15dovetail tool: delete unnecessary prepare_env.pyMatthewLi1-13/+20
JIRA: DOVETAIL-181 Change-Id: I6e79467b829b4ae1d815bdb9ead0b930f0338cd2 Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2017-01-05release tag supportMatthewLi1-0/+30
JIRA: DOVETAIL-170 Change-Id: Id56e30fdb3fb5b652e2145dd406b71986997f200 Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2016-12-16Merge "dovetail tool: document for dovetail CLI"hongbo tian2-0/+181
2016-12-13bugfix of document errorMatthewLi4-16/+11
JIRA: DOVETAIL-155 errors can refer to https://build.opnfv.org/ci/job/opnfv-docs-verify-master/3727/console Change-Id: I19e96239c8183bafca731477723615caff71388b Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2016-12-13Merge "[WIP] Migrate to tox based environment"hongbo tian7-11/+12
2016-12-13[WIP] Migrate to tox based environmentLeif Madsen7-11/+12
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>
2016-12-13Merge "Add more document and fix dockerfile for CentOS"hongbo tian1-2/+10
2016-12-09Add more document and fix dockerfile for CentOSTomofumi Hayashi1-2/+10
Add how to build container from dockerfile and add missing config for CentOS dockerfile. This fix is verified that functest/yeardstick are called successfully under debug/proposed_tests testsuite. Change-Id: Icb31331ecd78b8fccd69ac960c24340b605e54bf Signed-off-by: Tomofumi Hayashi <tohayash@redhat.com>
2016-12-082 config files description documentsMatthewLi1-0/+16
JIRA: DOVETAIL-50 Change-Id: I65c618ce3de78677b9e66a1c2d7f0af705e80cfb Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2016-12-07dovetail tool: document for dovetail CLIxudan2-0/+181
1. document for developers about how to add or delete commands by modifying cmd_config.yml file. 2. document for users about how to run dovetail tool with CLI JIRA: DOVETAIL-25 Change-Id: Iecf9d7a230e694bdda5634a87f7e5ddf7b7a57fd Signed-off-by: xudan <xudan16@huawei.com>
2016-12-06[RFC]Add dockerfile to support dovetail in CentOSTomofumi Hayashi1-0/+3
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>
2016-11-26dovetail tool: testarea argument addedMatthewLi2-12/+16
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>
2016-11-10dovetail tool: 2 config files, compliance_set and proposed_testsMatthewLi1-9/+9
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>
2016-10-26dovetail tool: developer userguide documentMatthewLi8-225/+246
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>
2016-10-11Add documentation for dovetail toolLeo Wang6-2/+338
JIRA:DOVETAIL-28 Change-Id: I2478655d951a65a11f39e9ceba10969e56274cc3 Signed-off-by: Leo Wang <grakiss.wanglei@huawei.com>
2016-09-27IPv6 test cases: Test case specification document exampleBin Hu5-44/+381
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>
2016-08-09Proposing a Dovetail test suite structure for IPv6ChristopherPrice7-0/+274
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>
2016-07-14project document reorganizationMatthewLi17-0/+42
JIRA: DOVETAIL-7 Change-Id: Ic17a05ea15858f6f93f112f26b532339f5904178 Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2016-03-07Remove trailing spacesDave Neary1-3/+3
2016-03-07Upodated INFO file for RST formatting.ChristopherPrice1-5/+5
Change-Id: I6a81e832a311096d70acabe3dba20e8736d74ea7 Signed-off-by: ChristopherPrice <christopher.price@ericsson.com>
2016-03-02Initial test plan structure for BrahmaputraLincoln Lavoie11-0/+266
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