diff options
Diffstat (limited to 'docs/com/pres')
| -rwxr-xr-x | docs/com/pres/testapi.html | 43 |
1 files changed, 30 insertions, 13 deletions
diff --git a/docs/com/pres/testapi.html b/docs/com/pres/testapi.html index 0f51251d..c27c21de 100755 --- a/docs/com/pres/testapi.html +++ b/docs/com/pres/testapi.html @@ -77,10 +77,15 @@ * Many locations (in VM, Jumphost, external DB,...) </section> <section data-markdown> + <script type='text/template'> ## Achieve using testAPI * Uniform API: testAPI * Uniform format: JSON * Universal Location: http://testresults.opnfv.org + <aside class='notes'> + By using testAPI, we hope to provide a uniform way of collection and saving test results to a universal location + </aside> + </script> </section> <section data-markdown> @@ -122,15 +127,21 @@ </section> <section> <h2>Colorado refactoring</h2> - <ul>Unit tests + <ul> + <li>Unit tests</li> <li>Update of the data model</li> - <li>Swagger tornado framework for the doc</li> + <li>Tornado_swagger for the documentation</li> <li>URL and MongoDB collection renaming</li> - <li>Scripts to support backup/restore/update DB</li> + <li>Scripts to support databse backup/restore/update</li> <li>Support installation</li> + <aside class='notes'> + So you can discover and understand the capabilities of the service without + access to source code, documentation, or through network traffic inspection, + and also you can interact with the testAPI directly through swagger website. + </aside> </ul> <p class="fragment fade-up"><b>All done in Colorado!</b></p> - </section> + </section> </section> <section> @@ -141,12 +152,12 @@ <section> <h2> URI changes...</h2> <div style="text-align:left""> - <p> testresults.opnfv.org/test/testapi => <br>testresults.opnfv.org/test/api/v1 </p> + <p> testresults.opnfv.org/<span style="color:lightblue">testapi</span> => <br>testresults.opnfv.org/<span style="color:yellow">test/api/v1</span> </p> - <p> http://testresults.opnfv.org/test/api/v1/<b>pods</b></p> - <p> http://testresults.opnfv.org/test/api/v1/<b>projects</b></p> - <p> http://testresults.opnfv.org/test/api/v1/projects/qtip/<b>cases</b></p> - <p> http://testresults.opnfv.org/test/api/v1/<b>results</b></p> + <p> /test/api/v1/<b>pods</b></p> + <p> /test/api/v1/<b>projects</b></p> + <p> /test/api/v1/projects/qtip/<b>cases</b></p> + <p> /test/api/v1/<b>results</b></p> </div> </section> <section data-markdown> @@ -160,15 +171,21 @@ | Item | Brahmaputra | Colorado | | :--- | :--- | :--- | | date | creation_date | start_date and stop_date | - | version | used as scenario | git version | + | version | used as scenario | opnfv release version | </section> <section data-markdown> + <script type='text/template'> ## New fields for results | Item | Colorado | | :--- | :--- | | scenario | used for scenario | - | criteria | Pass/Failed | + | criteria | PASS/FAILED | | trust_indicator | between 0 and 1| + <aside class='notes'> + to detect if the test case is stable over time and further more to avoid + running it systematically and saving time for other long duration test cases + </aside> + </script> </section> <section data-markdown> ## One new filter for results @@ -206,8 +223,8 @@ OK </section> <section data-markdown> ## Roadmap - * Dockerized testAPI - * Integration with Kibana + * Dockerize testAPI + * Automatic update of testAPI * Command Line Interface * Automatic update for pods/projects/testcases </section> |