From e44cbdc552169528ee9293f329d705971da8eec5 Mon Sep 17 00:00:00 2001 From: Vitalii Yerys Date: Wed, 3 Aug 2016 13:20:39 +0300 Subject: [PATCH] Added doc folder for plugin documentation. Created master test plan. Change-Id: I4e31cd060c3582724782b76b482558fb61fcec30 --- doc/testing/master_test_plan.rst | 222 +++++++++++++++++++++++++++ doc/testing/test_suite_smoke_bvt.rst | 82 ++++++++++ 2 files changed, 304 insertions(+) create mode 100644 doc/testing/master_test_plan.rst create mode 100644 doc/testing/test_suite_smoke_bvt.rst diff --git a/doc/testing/master_test_plan.rst b/doc/testing/master_test_plan.rst new file mode 100644 index 0000000..3110dde --- /dev/null +++ b/doc/testing/master_test_plan.rst @@ -0,0 +1,222 @@ +===================================================== +Master test plan for Google cloud storage fuel plugin +===================================================== + + +1. Introduction +--------------- + + +1.1 Purpose +########### + + This document describes Master Test Plan for GCS Fuel Plugin. The scope of + this plan defines the following objectives: + + - describe testing activities; + - outline testing approach, test types, test cycles that will be used; + - test mission; + - deliverables; + + +1.2 Intended Audience +##################### + + This document is intended for GCS project team staff (QA and Dev engineers + and managers) all other persons who are interested in testing results. + + +2. Governing Evaluation Mission +------------------------------- + +GCS plugin for Fuel provides the functionality to add backup option to +Google Cloud for Mirantis OpenStack. It uses Fuel plugin architecture along +with pluggable architecture enhancements introduced in latest Mirantis +OpenStack Fuel. +The plugin must be compatible with the version 9.0 of Mirantis OpenStack. + + +2.1 Evaluation Test Mission +########################### + + - Lab environment deployment. + - Deploy MOS with developed plugin installed. + - Create and run specific tests for plugin/deployment. + - Documentation + + +2.2 Test Items +############## + + - Fuel GCS plugin UI setup page, default values tested automatically, + other scenarios will be tested manually; + - Fuel CLI; + - Fuel API; + - Fuel UI; + - MOS; + - MOS API. + + +3. Test Approach +---------------- + +The project test approach consists of BVT, Integration/System, Regression and +Acceptance test levels. + + +3.1 Criteria for test process starting +###################################### + + Before test process can be started it is needed to make some preparation + actions - to execute important preconditions. The following steps must be + executed successfully for starting test phase: + + - all project requirements are reviewed and confirmed; + - implementation of testing features has finished (a new build is ready for + testing); + - implementation code is stored in GIT; + - bvt-tests are executed successfully (100% success); + - test environment is prepared with correct configuration; + - test environment contains the last delivered build for testing; + - test plan is ready and confirmed internally; + - implementation of manual tests and necessary autotests has finished. + + +3.2 Suspension Criteria +####################### + + Testing of a particular feature is suspended if there is a blocking issue + which prevents tests execution. Blocking issue can be one of the following: + + - Feature has a blocking defect, which prevents further usage of this feature + and there is no workaround available; + - CI test automation scripts failure. + + +3.3 Feature Testing Exit Criteria +################################# + + Testing of a feature can be finished when: + + - All planned tests (prepared before) for the feature are executed; no + defects are found during this run; + - All planned tests for the feature are executed; defects found during this + run are verified or confirmed to be acceptable (known issues); + - The time for testing of that feature according to the project plan has run + out and Project Manager confirms that no changes to the schedule are + possible. + + +4. Deliverables +--------------- + + +4.1 List of deliverables +######################## + + Project testing activities are to be resulted in the following reporting + documents: + + - Test plan; + - Test run report; + + +4.2 Acceptance criteria +####################### + + 90% of tests cases should be with status - passed. Critical and high issues + are fixed. Such manual tests should be executed and passed (100% of them): + + - Deploy cluster with GCS plugin enabled. + + - Boot VM with proper image. + - Create a snapshot of recently booted vm. + - Backup that snapshot on a GCS. + - Destroy VM. + - Download the snapshot from a GCS. + - Boot VM with downloaded from GCS snapshot. + + +5. Test Cycle Structure +----------------------- + +An ordinary test cycle for each iteration consists of the following steps: + + - Smoke testing of each build ready for testing; + - Verification testing of each build ready for testing; + - Regression testing cycles in the end of iteration; + - Creation of a new test case for covering of a new found bug (if such test + does not exist). + + +5.1.1 Smoke Testing +################### + + Smoke testing is intended to check a correct work of a system after new + build delivery. Smoke tests allow to be sure that all main system + functions/features work correctly according to customer requirements. + + +5.1.2 Verification testing +########################## + + Verification testing includes functional testing covering the following: + + - new functionality (implemented in the current build); + - critical and major defect fixes (introduced in the current build). + + Some iteration test cycles also include non-functional testing types + described in Overview of Planned Tests. + + +5.1.3 Regression testing +######################## + + Regression testing includes execution of a set of test cases for features + implemented before current iteration to ensure that following modifications + of the system haven't introduced or uncovered software defects. It also + includes verification of minor defect fixes introduced in the current + iteration. + + +5.1.4 Bug coverage by new test case +################################### + + Bug detection starts after all manual and automated tests are prepared and + test process initiated. Ideally, each bug must be clearly documented and + covered by test case. If a bug without a test coverage was found it must + be clearly documented and covered by custom test case to prevent occurrence + of this bug in future deployments/releases etc. All custom manual test + cases suppose to be added into TestRail and automated tests suppose to be + pushed to Git/Gerrit repo. + + +5.2 Performance testing +####################### + + Performance testing will be executed on the scale lab and a custom set of + Rally scenarios (or other performance tool) must be executed with GCS + environment. + + +5.3 Metrics +########### + + Test case metrics are aimed to estimate a quality of bug fixing; detect not + executed tests and schedule their execution. Passed / Failed test cases - + this metric shows results of test cases execution, especially, a ratio + between test cases passed successfully and failed ones. Such statistics must + be gathered after each delivered build test. This will help to identify a + progress in successful bugs fixing. Ideally, a count of failed test cases + should aim to a zero. + Not Run test cases - this metric shows a count of test cases which should be + run within a current test phase (have not run yet). Having such statistics, + there is an opportunity to detect and analyze a scope of not run test cases, + causes of their non execution and planning of their further execution + (detect time frames, responsible QA). + + +6. Test scope +------------- + +.. include:: test_suite_somke_bvt.rst diff --git a/doc/testing/test_suite_smoke_bvt.rst b/doc/testing/test_suite_smoke_bvt.rst new file mode 100644 index 0000000..7a088cc --- /dev/null +++ b/doc/testing/test_suite_smoke_bvt.rst @@ -0,0 +1,82 @@ +========= +BVT tests +========= + + +Smoke test +---------- + + +ID +## + +gcs_deploy_smoke + +Description +########### + +Smoke test for Google Cloud Storage fuel plugin. Deploy cluster with +controller, compute and cinder nodes and install plugin. + +Complexity +########## + +core + +Steps +##### + + 1. Upload plugin to the master node + 2. Install plugin + 3. Create cluster + 4. Add 1 nodes with controller role + 5. Add 1 node with compute role + 6. Add 1 node with cinder role + 7. Deploy the cluster + +Expected results +################ + +All steps must be completed successfully, without any errors. + + + +BVT test +-------- + + +ID +## + + +gcs_deploy_bvt + +Description +########### + +BVT test for Google Cloud Storage fuel plugin. Deploy cluster in HA mode with +3 controllers, compute and cinder nodes and install plugin. + +Complexity +########## + +core + +Steps +##### + + 1. Upload plugin to the master node + 2. Install plugin + 3. Create cluster + 4. Add 3 nodes with controller role + 5. Add 1 node with compute role + 6. Add 1 node with cinder role + 7. Deploy the cluster + 8. Run network verification + 9. Check plugin installation + 10. Run OSTF + +Expected results +################ + +All steps must be completed successfully, without any errors.