From f0c3ce2258b38e852174fde7cf668017587702a8 Mon Sep 17 00:00:00 2001 From: madavi Date: Thu, 1 Aug 2019 14:28:27 +0530 Subject: [PATCH] New feature request: RobotFramework for build Test Change-Id: I10aeb239872e4842b36aab73836efd1444b90a8e Signed-off-by: madavi --- Release7/Robot_Integration_Tests.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 Release7/Robot_Integration_Tests.md diff --git a/Release7/Robot_Integration_Tests.md b/Release7/Robot_Integration_Tests.md new file mode 100644 index 0000000..b9c1799 --- /dev/null +++ b/Release7/Robot_Integration_Tests.md @@ -0,0 +1,19 @@ +# Robot integration framework for builds verification # + +## Proposer ## +Jayant Madavi +Mrityunjay Yadav + +## Type ## +**Feature** + +## Target MDG/TF ## +**DevOps** + +## Description ## +Currently OSM supports many types of [VIMs](https://osm.etsi.org/wikipub/index.php/VIMs) ex Openstack, VMware, Openvim, AWS etc. For each supported VIMs test cases are executed manually. Today for each release, based on the features/bug fix, test cases are identified and results are captured in [xls](https://osm.etsi.org/wiki/index.php/Release_SIX_Integration_(DEVOPS)). These test cases can be classified based on VIMs as Core_TestCases, featureOrBug_TestCases. +Using robot framework will ease certifying the build. Also at the same time will create incremental repository of comprehensive test cases, for the upcoming build/releases. +Robot framework is going to generate the report, after every stage-4 build. Based on these reports, a build can be classified as Successful, partially successful or failed. + +## Demo or definition of done ## +Run the agreed set of test cases for each build/release. Check the output report for success/failure. \ No newline at end of file -- 2.25.1