aboutsummaryrefslogtreecommitdiffstats
path: root/kud
diff options
context:
space:
mode:
authorKonrad Bańka <k.banka@samsung.com>2019-07-15 15:00:09 +0200
committerKonrad Bańka <k.banka@samsung.com>2019-07-15 15:02:41 +0200
commit30bd837f31755aa018d7226f28798e324ff01484 (patch)
tree7bd44c8dcc3a3570b3d7c8be3eec5ba85828d9c4 /kud
parent670a20f33a2b741a6a5e7c7c4f7dfc9e16378a75 (diff)
Fix istio test scenario endpoint API validation
Current query issued at the end of testcase to istio service API didn't validate the case, when http server responded with 5XX http code. By reusing common wrapper for cURL, this is now handled properly. Issue-ID: MULTICLOUD-686 Signed-off-by: Konrad Bańka <k.banka@samsung.com> Change-Id: Ifb73494c9a6d98143edccaad095b2de5d456ef4f
Diffstat (limited to 'kud')
-rwxr-xr-xkud/tests/istio.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/kud/tests/istio.sh b/kud/tests/istio.sh
index c525bb8e..e9ef00c6 100755
--- a/kud/tests/istio.sh
+++ b/kud/tests/istio.sh
@@ -36,5 +36,5 @@ for deployment in details-v1 productpage-v1 ratings-v1 reviews-v1 reviews-v2 rev
done
INGRESS_PORT=$(kubectl -n istio-system get service istio-ingressgateway -o jsonpath='{.spec.ports[?(@.name=="http2")].nodePort}')
INGRESS_HOST=$(kubectl get po -l istio=ingressgateway -n istio-system -o 'jsonpath={.items[0].status.hostIP}')
-curl -o /dev/null -s -w "%{http_code}\n" http://$INGRESS_HOST:$INGRESS_PORT/productpage
+call_api http://$INGRESS_HOST:$INGRESS_PORT/productpage >/dev/null
popd