new examples

Author: fmancardi

rest-api/v1/curl/generic/createTestCaseX.sh

@@ -0,0 +1,22 @@
+#!/usr/bin/sh
+# curl -i -X POST -u dev01:dev01 http://localhost/development/tlrepo/lib/api/rest/v1/testprojects
+# -i include headers
+# -X (HTTP) Specifies a custom request method to use when communicating with the HTTP server  
+# -u user:password
+# --data If you start the data with the letter @, the rest should be a file name to read the data from, 
+#        or - if you want curl to read the data from stdin. 
+#        The contents of the file must already be URL-encoded. 
+#        Multiple files can also be specified. 
+#        Posting data from a file named 'foobar' would thus be done with --data @foobar.
+#
+clear
+echo 'Testing TestLink REST API - POST /testcases'
+echo 
+if [ -z "$1" ]; then 
+   echo usage: $0 .JSONFILE \(searched in ../json/\)
+   exit
+fi
+
+curl -i -H "Content-Type: application/json" -X POST --data "@../json/$1" \
+     -u restadminapikey:followthewitherabbitneo \
+     http://localhost/development/tlrepo/lib/api/rest/v1/testcases

rest-api/v1/curl/json/createTestCaseB.json

@@ -0,0 +1,11 @@
+{
+  "name":"Test Case ALFA",
+  "testSuiteID":360,
+  "testProjectID":358,
+  "summary":"This is a summary for Test Case",
+  "preconditions":"No preconditions",
+  "order":100,
+  "authorID":1,
+  "importance":2,
+  "executionType":1,
+}

rest-api/v1/curl/json/createTestCaseXL5.json

@@ -0,0 +1,11 @@
+{
+  "name":"Test Case XL5-A",
+  "testSuiteID":378,
+  "testProjectID":														358,
+  "summary": "This is a summary for Test Case second line line #3",
+  "preconditions":"No preconditions",
+  "order":100,
+  "authorID":1,
+  "importance":2,
+  "executionType":1
+}

rest-api/v1/curl/json/createTestCaseXL5B.json

@@ -0,0 +1,10 @@
+{
+  "name":"Test Case XL5-B",
+  "testSuiteID":378,"testProjectID":358,
+  "summary": 
+  "This is a summary for Test Case 
+  second line 
+  line #3",
+  "preconditions":"No preconditions",
+  "order":100,"authorID":1,"importance":2,"executionType":1
+}

rest-api/v1/curl/json/createTestCaseXL5C.json

@@ -0,0 +1,10 @@
+{
+  "name":"Test Case XL5-C",
+  "testSuiteID":378,"testProjectID":358,
+  "summary": 
+  "This is a summary for Test Case 
+  second line 
+  line #3",
+  "preconditions":"No preconditions",
+  "order":100,"authorID":1,"importance":2,"executionType":1
+}

rest-api/v1/curl/json/createTestCaseXL5D.json

@@ -0,0 +1,12 @@
+{
+  "name":"Test Case XL5-D",
+  "testSuiteID":378,"testProjectID":358,
+  "summary": 
+  "This is a summary for Test Case <br>
+  second line <br>
+  line #3",
+  "preconditions":"No preconditions for this testcase. 
+  <br>If you use an array [] can be empty
+  <br>If you need to use a object {}",
+  "order":100,"authorID":1,"importance":2,"executionType":1
+}

rest-api/v1/curl/json/testCaseComplex.json

@@ -0,0 +1,16 @@
+{
+  "name":"Test Scenarios for Filter Criteria",
+  "testSuiteID":378,"testProjectID":358,
+  "preconditions":"No preconditions for this testcase. 
+  <br>If you use an array [] can be empty
+  <br>If you need to use a object {}",
+  "order":100,"authorID":1,"importance":2,"executionType":1,
+  "summary": 
+  "<br>1. User should be able to filter results using all parameters on the page
+   <br>2. Refine search functionality should load search page with all user selected search parameters
+   <br>3. When there is at least one filter criteria is required to perform search operation, 
+   <br>   make sure proper error message is displayed when user submits the page without selecting any filter criteria.
+   <br>4. When at least one filter criteria selection is not compulsory user 
+   <br>   should be able to submit page and default search criteria should get used to query results
+  <br>5. Proper validation messages should be displayed for invalid values for filter criteria"
+}