+
# Agenda
- * A test API: what for?
+ * testAPI: what for?
* API overview
* API evolution
+ * Roadmap
-
-
- # A test API: what for?
-
-
- ## Give a consistant view for
- * Test projects
- * Test cases
- * Test resources (Pods)
- * Test results
-
-
-
- ## Unify result display
- * From many projects
- * Many formats (log, html, json, ..)
- * Many locations (in VM, Jumphost, external DB,...)
-
-
-
- ## Help building
- * Dashboards
- * Automatic reporting
-
-
-
-
-
- # API overview
-
-
- ## API in Brahmaputra
- * Tornado + MongoDB
- * Simple data models aggreed with the testing group
- * No unit tests
- * Wiki and rst documentation
-
-
-
- ## API in Brahmaputra
- 
-
-
- ## API in Brahmaputra
- 
- https://wiki.opnfv.org/display/functest/Collection+Of+Test+Results
-
-
-
- ## Lessons learned in B.
- * Wiki documentation is painful
- * result modl too simple
- * version used for scenario
- * no version
- * no overall criteria (passed/failed)
- * need unit tests for data model evolution
-
-
- ## Colorado refactoring
- * done by Serena Feng (ZTE)
- * update of the data model (based on lesson learned)
- * creation of a swagger tornado framework for the doc
- * creation of unit tests
-
-
-
-
-
- #API evolution
-
-
-
Test API evolution
-
-
-
-
Field
-
Brahmaputra
-
Colorado
-
-
-
-
-
date
-
creation_date
-
start_date and stop_date
-
-
-
version
-
used as scenario
-
git version
-
-
-
scenario
-
N.R
-
used for scenario
-
-
-
test_criteria
-
N.R
-
passed/failed
-
-
-
trust_indictator
-
N.R
-
between 0 and 1
-
-
-
last
-
N.R
-
get last N results
-
-
-
-
-
- ## Swagger doc
+
+
+ # test API: what for?
+
+
+ ## Consistant view for
+ * Resources (Pods)
+ * Projects
+ * Test cases
+ * Results
+
+
+
+ ## Status Currently
+ * From many projects
+ * Many formats (log, html, json, ..)
+ * Many locations (in VM, Jumphost, external DB,...)
+
+
+
+
+
+
+ ## Help building
+ * Dashboards
+ * Automatic reporting
+
+
+
+
+
+ # API overview
+
+
+ ## Storage structure
+ 
+
+
+ ## API in Brahmaputra
+ 
+ https://wiki.opnfv.org/display/functest/Collection+Of+Test+Results
+
+
+
+ ## API status in Brahmaputra
+ * Simple data models aggreed with the testing group
+ * No unit tests
+ * Wiki and rst documentation
+
+
+
+ ## Lessons learned in B.
+ * Painful wiki documentation
+ * Simple result model
+ * Misuse version as scenario
+ * No version actually
+ * No overall criteria (PASS/FAIL)
+ * Difficult refactoring
+
+
+
+
+
+ ## One new field for pods
+ | Field | Colorado |
+ | :--- | :--- |
+ | role | community_pod, ci_pod, .. |
+
+
+ ## Changed fields for results
+ | Item | Brahmaputra | Colorado |
+ | :--- | :--- | :--- |
+ | date | creation_date | start_date and stop_date |
+ | version | used as scenario | opnfv release version |
+
+
+
+
+
+ ## One new filter for results
+ | Item | Colorado |
+ | :--- | :--- |
+ | last | get last N results|
+
+
+ http://testresults.opnfv.org/test/swagger/spec.html

-
-
-
unit tests
-
+
+
+
unit tests
+
umry8364@umry8364-Latitude-E6400:~/Dev/OPNFV/releng/utils/test/result_collection_api$ ./run_test.sh
Tests running...
WARNING:tornado.general:404 GET /dashboard/v1/results?case=vPing&pod=zte-pod1&version=C&installer=fuel&period=5 (127.0.0.1): Project name missing
@@ -190,18 +213,33 @@ WARNING:tornado.access:404 PUT /api/v1/projects/functest/cases/notFound (127.0.0
Ran 74 tests in 1.848s
OK
-