From 817dec9434548e3c3d12d73415410f870722b375 Mon Sep 17 00:00:00 2001
From: SerenaFeng <feng.xiaowei@zte.com.cn>
Date: Thu, 2 Mar 2017 11:06:55 +0800
Subject: unify TestAPI naming

TestAPI naming in documents is quite arbitrary, test api/testapi/Test
API/testApi/TestApi..., this patch aims to give it a formal name TestAPI

Change-Id: I9ea91418814352d3176df3f35598b6c5929b1dae
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
---
 .../com/pres/Summit/Berlin-2016/summit-Berlin.html |  2 +-
 docs/com/pres/Summit/Berlin-2016/testapi.html      | 28 +++++++++++-----------
 2 files changed, 15 insertions(+), 15 deletions(-)

(limited to 'docs/com/pres/Summit')

diff --git a/docs/com/pres/Summit/Berlin-2016/summit-Berlin.html b/docs/com/pres/Summit/Berlin-2016/summit-Berlin.html
index 4173a86ac..8369443f7 100755
--- a/docs/com/pres/Summit/Berlin-2016/summit-Berlin.html
+++ b/docs/com/pres/Summit/Berlin-2016/summit-Berlin.html
@@ -230,7 +230,7 @@
 						## What's new?
 						* Slicing of the tests (healthcheck / Smoke / SDN controllers / Features / Components / VNFs)
 						* Better Test duration management
-						* Refactoring (repo, case management, test API)
+						* Refactoring (repo, case management, TestAPI)
 						* Automatic reporting
 						* Dashboard evolution to ELK
 						* CLI
diff --git a/docs/com/pres/Summit/Berlin-2016/testapi.html b/docs/com/pres/Summit/Berlin-2016/testapi.html
index 7035d71df..16f97c44d 100755
--- a/docs/com/pres/Summit/Berlin-2016/testapi.html
+++ b/docs/com/pres/Summit/Berlin-2016/testapi.html
@@ -6,7 +6,7 @@
 
 		<title>OPNFV presentation</title>
 
-		<meta name="description" content="Test API">
+		<meta name="description" content="TestAPI">
 		<meta name="author" content="Serena Feng">
 
 		<meta name="apple-mobile-web-app-capable" content="yes" />
@@ -42,7 +42,7 @@
 
 				<section data-background="../../../img/title-bg-berlin.png" data-background-transition="none">
 					<br><br><br><br><br>
-					<h1>Test API</h1>
+					<h1>TestAPI</h1>
 					<h3>Clean, Easy, Complete</h3>
 					<br>
 						<h4>OPNFV testing community</h4>
@@ -52,7 +52,7 @@
 
 				<section data-markdown>
 					# Agenda
-					* testAPI: what for?
+					* TestAPI: what for?
 					* API overview
 					* API evolution
 					* Roadmap
@@ -60,7 +60,7 @@
 
 				<section>
 					<section data-markdown>
-						# test API: what for?
+						# TestAPI: what for?
 					</section>
 					<section data-markdown>
 						## Consistant view for
@@ -78,12 +78,12 @@
 					</section>
 					<section data-markdown>
 						<script type='text/template'>
-						## Achieve using testAPI
-						* Uniform API: testAPI
+						## 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
+							By using TestAPI, we hope to provide a uniform way of collection and saving test results to a universal location
 						</aside>
 						</script>
 					</section>
@@ -101,11 +101,11 @@
 					</section>
 					<section data-markdown>
 						## Storage structure
-						![testapi](https://wiki.opnfv.org/download/attachments/2926452/results_collection_structure.png?version=1&modificationDate=1459196347000&api=v2 "OPNFV API page")
+						![TestAPI](https://wiki.opnfv.org/download/attachments/2926452/results_collection_structure.png?version=1&modificationDate=1459196347000&api=v2 "OPNFV API page")
 					</section>
 					<section data-markdown>
 						## API in Brahmaputra
-						![testapi](../../../img/testapi0.png)
+						![TestAPI](../../../img/testapi0.png)
 						https://wiki.opnfv.org/display/functest/Collection+Of+Test+Results
 					</section>
 
@@ -137,7 +137,7 @@
                         <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.
+                            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>
@@ -152,7 +152,7 @@
 					<section>
 						<h2> URI changes...</h2>
 						<div style="text-align:left""> 
-							<p> testresults.opnfv.org/<span style="color:lightblue">testapi</span> => <br>testresults.opnfv.org/<span style="color:yellow">test/api/v1</span> </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> /test/api/v1/<b>pods</b></p>
 							<p> /test/api/v1/<b>projects</b></p>
@@ -195,7 +195,7 @@
 					</section>
 					<section data-markdown>
 						http://testresults.opnfv.org/test/swagger/spec.html
-						![alt text](../../../img/testapi1.png "Test API swagger interface")
+						![alt text](../../../img/testapi1.png "TestAPI swagger interface")
 					</section>
 					<section>
 						<h2>unit tests</h2>
@@ -223,8 +223,8 @@ OK
 					</section>
 					<section data-markdown>
 						## Roadmap
-						* Dockerize testAPI
-						* Automatic update of testAPI
+						* Dockerize TestAPI
+						* Automatic update of TestAPI
 						* Command Line Interface
 						* Automatic update for pods/projects/testcases
 					</section>
-- 
cgit 1.2.3-korg