User Tools

Site Tools



This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
opnfv_functional_testing [2015/08/24 07:07]
Morgan Richomme [Functest versus Release]
opnfv_functional_testing [2016/03/01 08:48] (current)
Ryota Mibu [Key Project Facts]
Line 1: Line 1:
 ====== Project: OPNFV - Base system functionality testing (Functest) ====== ====== Project: OPNFV - Base system functionality testing (Functest) ======
-  * //Proposed name for the project:// **OPNFV – Base system functionality testing** +  * Project NameFunctest \\ 
-  * //Proposed name for the repository:// **functest** +  * Project Repository: functest ​\\ 
-  * //Project ​Categories:// Integration & Testing +  * Project ​Category: Integration & Testing ​\\ 
-  * //project Etherpad:// https://​​p/​functiontestrelease1activities +  * Project ​IRC chan: #​opnfv-testperf ​\\ 
-  * //IRC chan:// #​opnfv-testperf +  * [[functest_meeting|Team meeting ​page]] \\ 
-  * //[[functest_meeting|weekly team meeting]]:// every Tuesday (4PM UTC) +  * [[functest_team|Functest ​Team]] ​\\ 
-  * //[[functest_team|Team]]//​+ 
 +^ {{:​information.png?​70|}} ^ **Quick links** \\ [[​secure/​RapidBoard.jspa?​rapidView=59&​view=detail&​selectedIssue=FUNCTEST-55|Functest Kanban board]] \\ [[https://​​secure/​Dashboard.jspa?​selectPageId=10611|Functest Jira Dashboard]] \\ [[https://​​functextnexttaks|Functest Brahmaputra page]] \\ [[opnfv_functional_testing#​Testcases|Testcases]]\\ [[opnfv_functional_testing#​Videos|Functest videos]] ^ 
Line 57: Line 58:
 Functional tests shall be Functional tests shall be
-  * independant ​from the installer (Fuel, Foreman/​Puppet,​ Juju,​..) ​+  * independent ​from the installer (Fuel, Foreman/​Puppet,​ Juju,​..) ​
   * automated and integrated in CI   * automated and integrated in CI
Line 63: Line 64:
 ===== Functest versus Release ===== ===== Functest versus Release =====
-[[functest_release_1| Functest for Release 1 ]]+[[functest_release_1| Functest for ARNO (Release 1]]
-[[FuncTextNextTaks| Functest for Release 2]].+[[functest_release_2| Functest for BRAHMAPUTRA (Release 2) ]] 
 +[[FuncTextNextTaks| Functest Next tasks]].
 ===== Testcases ===== ===== Testcases =====
Line 86: Line 89:
 [[https://​​vnf_deployment_test_cases|Study on VNF deployment]] [[https://​​vnf_deployment_test_cases|Study on VNF deployment]]
-===== Dependencies ​=====+===== Videos ​=====
-  * The project is a contributor to project “Octopus”. +[[​v=7IO6t3C_OFA | Functest demo for Arno SR0]]
-  * The project leverages ​ "Boot Strap/Get Started"​ +
-  * The project relies on the following upstream projects: +
-    * OpenStack Juno release: Components: Nova, Glance, Keystone, Horizon, Neutron, Ceilometer, Heat +
-    * OpenDaylight Helium release: Components: MDSAL, OVSDB, RESTCONF, ML2 plugin/ODL Neutron drivers +
-    * Installer: TBD +
-    * Puppet (for instance configuration) +
-    * QEMU/KVM +
-    * OpenWRT (as example VNF - for routing, firewall, NAT) +
-    * Snort (as example VNF - for IDS) +
-    * Linux   ​Ubuntu 14.04/Centos 7 distribution+
 +===== Tips =====
 +==== Short story on Functest versus the other test projects and the installers ====
 +First of all we try to be as agnostic as possible.
 +we see OPNFV as a black box.
 +We automatically run functest-{installer}-master after a successful fresh installation of {installer}
 +In functest (and in yardstick) we have internal test cases and companion test projects
 +the functest companion projects dealing with functional testing are
 +  * doctor
 +  * copper
 +  * ovno
 +  * policyTest
 +  * promise
 +  * sdnvpn
 +companion project means that we wil onboard them in Functest CI process. After a fresh install, functest will be started (a docker file) running several tests one after the others (e.g. https://​​ci/​view/​functest/​job/​functest-fuel-master/​lastSuccessfulBuild/​consoleText) including companion tests in the near future.
 +each test may need specific env, so functest can install tooling and triggers scripts to setup env
 +we will also create a filtering mechanism to run tests only when possible (assuming that by default it is always possible) but no need to run odl suite towards an OPNFV including onos
 +In functest we developed ​ the code for our internal tests (scripts, tests, integration of upstream test suites,...)
 +The companion projects are in charge of their scripts, their code, their scenario...
 +we mutualize the CI env (running on target CI production labs), the tooling (some projects need for instance to run upstream ODL suite, functest install once robot and mininet for all of them, Rally may test module used by feature project (eg; congress/​copper)),​ the reporting, the documentation
 +Then jenkins functest-{installer} job will produce results that will be pushed in the Test collection DB
 +before Release B we will look carefully to the jobs (success criteria for Functest for B-Release is 4 successfull run on CI of the onboarded projects)
 +  * if errors in integration or internal cases => we will blame ourselves
 +  * if erros in companion projects => we will report the issues to the member of the feature projects
 +So you can see that we did not do specific stuff for 1 installer.
 +We have some adaptations of course in our scripts (e.g. to retrieve the credentials - not the same way on the different installers) but we do not create a plugin for a given installers, we have a docker file.
 +Functest (as yardstick) docker file could even be almost used towards any OPNFV-like solution (some adaptations on the env setup) ​
 +==== Git ====
 +Dealing with Branches
 +Best practice => Cherry Pick from Master to Stable useful patches as described in [[releases:​stablebranch|Stable Branch]]
 +If you forgot that (it may happen and we experienced that for SR1) as Master and stable may be considered as the same, you may have to merge Master on Stable...and then winter is a procedure that works:
 +  ​
 +   * git clone ssh://<​Your_ID_assuming_you_have_the_merge_rights>​​29418/​functest functest-clean
 +   * git checkout stable/arno
 +   * git merge master
 +   * git push origin HEAD:​refs/​for/​stable/​arno.
 ---- ----
Line 113: Line 155:
     * Kevin Riley (     * Kevin Riley (
     * Justin Hart ( ​     * Justin Hart ( ​
 +    * Ryota Mibu (
 Want to Join: [[https://​​ns=%3A&​image=%3Aopnfv-_functest.pdf&​do=media&​tab_files=files&​tab_details=view| know more on Functest]] Want to Join: [[https://​​ns=%3A&​image=%3Aopnfv-_functest.pdf&​do=media&​tab_files=files&​tab_details=view| know more on Functest]]
- ==== Planned deliverables ==== 
-Project deliverable:​ 
-The project delivers the following components: 
-  * Documentation of Test Suites and test cases that cover the OPNFV platform functionality testing including pass/fail criteria. 
-  * Test software and scripts for testing OPNFV Platform functionality that is essentially broken down into two main suites as follows: 
-    * OPNFV Platform Smoke test suite: ​ A sanity testing suite for basic verification of the platform. 
-    * OPNFV Platform Regression test suite: A comprehensive collection of detailed test suites. 
-  * Automated Test Framework based on Tempest/​Robot/​Jenkins,​ with necessary scripts and tools to automatically test and verify OPNFV functionality 
-=== Proposed Release Schedule ==== 
-OPNFV release #1.+{{:​devtest_journey.pdf|Tester Journey}}
opnfv_functional_testing.1440400039.txt.gz · Last modified: 2015/08/24 07:07 by Morgan Richomme