summaryrefslogtreecommitdiffstats
path: root/docs/testing
AgeCommit message (Collapse)AuthorFilesLines
2017-04-10Adding the submdules directory for openretrieverMatthewLi1-1/+3
see verify failure in https://gerrit.opnfv.org/gerrit/#/c/33199/ this patch aims to fix the rtd failure Change-Id: I7beed908835ff9ef2b9a07335757cccf0dc9b58b Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2017-03-31Fix storperf pathShubhamRathi1-1/+1
Change-Id: I0b7b6939668b96cda1360abb01ee4832293d450f Signed-off-by: ShubhamRathi <shubhamiiitbackup@gmail.com>
2017-03-31Update docsShubhamRathi1-0/+9
1. Add Functest Link using labels 2. Add storperf in testing-user Change-Id: If371ca17b8fdf8f54fefe5176d8a4f49e8a20981 Signed-off-by: ShubhamRathi <shubhamiiitbackup@gmail.com>
2017-03-31Add yardstick release note and devguideJingLu51-0/+8
Change-Id: Ic41a21055b51e4feed89208e87d474527e008fd5 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-03-30Add labels to composite docsShubhamRathi1-0/+2
Change-Id: I1b543c7f6236d72e627a0bebe174f915f607d907 Signed-off-by: ShubhamRathi <shubhamiiitbackup@gmail.com>
2017-03-30Merge "bug fix: bad table format"Sofia Wallin1-2/+2
2017-03-30Refactor documentsShubhamRathi2-8/+2
1. Remove projects not part of Danube from release notes 2. Remove redundant content about Test Frameworks from Installation Instroduction 3. Remove Yardstick from Testing Dev guide Change-Id: I8b14d76f2b43c89ebdf8d9e6a62ff3c4a22eae30 Signed-off-by: ShubhamRathi <shubhamiiitbackup@gmail.com>
2017-03-30bug fix: bad table formatMorgan Richomme1-2/+2
change on Cperf description lead to a table format error preventing the whole table to be displayed Change-Id: Ia18dfbba561610b74d1b10d2c5c3b86c14b51750 Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-03-29Expand CPerf overview docsDaniel Farrell1-1/+5
Change-Id: I82a53de2447b26e8fcfcc7ce556a318ce6f88cd7 Signed-off-by: Daniel Farrell <dfarrell07@gmail.com>
2017-03-29Update Testing ecosystem documentationMorgan Richomme1-111/+43
- new ecosystem figure - add reporting figure - indicate next steps for Danube 2.0 pending question (cperf) Change-Id: I3dcf5a4874f0585f433a693117764641aab8faf8 Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-03-28Updated VSPERF description and fixed Wiki links to projectTrevor Cooper1-3/+3
Change-Id: Ic71f8004621dbb99715907ba3d82acd0f20e2291 Signed-off-by: Trevor Cooper <trevor.cooper@intel.com>
2017-03-25Re-order testing user guide index pageYujun Zhang1-4/+4
Testing tools needs to be configured before use. Change-Id: I04862af1c9d2ee8d9fdb91397c3e18da2207a964 Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
2017-03-24Updated vsperf doc refs for release-notes and testingTrevor Cooper2-1/+19
Change-Id: I736ff7c5699e5be929ebe9104a0dfc619ef0ebc8 Signed-off-by: Trevor Cooper <trevor.cooper@intel.com>
2017-03-22Few minor edits plus used the SPDX license identifierRay Paik1-10/+10
Change-Id: Ibdd3c700bdf0ed8f67d5cd794568a99c2d0efab9 Signed-off-by: Ray Paik <rpaik@linuxfoundation.org>
2017-03-22qtip: correct project name letter caseYujun Zhang2-2/+2
As a project name, uppercase i.e. QTIP is preferred Change-Id: Id19e50f9f593c1eb0afbf6604bca3314f6223587 Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
2017-03-22Segregating Testing docShubhamRathi2-0/+78
Testing documentation has been segregated under 'User Guides' & 'Developer Guides' as decided by the test teams. Change-Id: I04a11ff88b329f4daad2ef020aefd0779d5a7ca5 Signed-off-by: ShubhamRathi <shubhamiiitbackup@gmail.com>
2017-03-19Misc ChangesShubhamRathi1-3/+3
1. Renamed ‘How to work with Documentation’ to Documentation Guide 2. Add Test Overview documentation breneath ‘Testing’ 3. Removed the index off Release Notes Change-Id: Iaef364f5ee59a99f906270271c1daf49cfae4c4f Signed-off-by: ShubhamRathi <shubhamiiitbackup@gmail.com>
2017-01-23Updated intro and vsperf project description.Trevor Cooper1-22/+22
Updates: Fixed review issues with trailing white spaces, Bottlenecks description and made further vsperf description edits. Change-Id: Id1c979f6365b022f27ab79ac7b75a42110e0150b Signed-off-by: Trevor Cooper <trevor.cooper@intel.com>
2017-01-19Update testing community docMorgan Richomme5-40/+339
Change-Id: I7ffbb3c0460958e3ecd837a14bf0c9a5752d1fc0 Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2016-11-24Adjusted the docs repo structure for D release workSofia Wallin4-0/+53
Change-Id: I9befe06c424c726e17d754bc480413b2430549ba Signed-off-by: Sofia Wallin <sofia.wallin@ericsson.com>
--------------------------------------------------+ |metrics | In this test case, there are two metrics: | | | 1)service_outage_time: which indicates the maximum outage | | | time (seconds) of the specified Openstack command request. | | | 2)process_recover_time: which indicates the maximun time | | | (seconds) from the process being killed to recovered | | | | +--------------+--------------------------------------------------------------+ |test tool | Developed by the project. Please see folder: | | | "yardstick/benchmark/scenarios/availability/ha_tools" | | | | +--------------+--------------------------------------------------------------+ |references | ETSI NFV REL001 | | | | +--------------+--------------------------------------------------------------+ |configuration | This test case needs two configuration files: | | | 1) test case file: opnfv_yardstick_tc019.yaml | | | -Attackers: see above "attackers" discription | | | -waiting_time: which is the time (seconds) from the process | | | being killed to stoping monitors the monitors | | | -Monitors: see above "monitors" discription | | | -SLA: see above "metrics" discription | | | | | | 2)POD file: pod.yaml | | | The POD configuration should record on pod.yaml first. | | | the "host" item in this test case will use the node name in | | | the pod.yaml. | | | | +--------------+--------------------------------------------------------------+ |test sequence | description and expected result | | | | +--------------+--------------------------------------------------------------+ |step 1 | start monitors: | | | each monitor will run with independently process | | | | | | Result: The monitor info will be collected. | | | | +--------------+--------------------------------------------------------------+ |step 2 | do attacker: connect the host through SSH, and then execute | | | the kill process script with param value specified by | | | "process_name" | | | | | | Result: Process will be killed. | | | | +--------------+--------------------------------------------------------------+ |step 3 | stop monitors after a period of time specified by | | | "waiting_time" | | | | | | Result: The monitor info will be aggregated. | | | | +--------------+--------------------------------------------------------------+ |step 4 | verify the SLA | | | | | | Result: The test case is passed or not. | | | | +--------------+--------------------------------------------------------------+ |post-action | It is the action when the test cases exist. It will check the| | | status of the specified process on the host, and restart the | | | process if it is not running for next test cases | | | | +--------------+--------------------------------------------------------------+ |test verdict | Fails only if SLA is not passed, or if there is a test case | | | execution problem. | | | | +--------------+--------------------------------------------------------------+