Add: test that one can retrieve resource type specs via API

1 files changed, 11 insertions, 2 deletions

diff --git a/yarns/smoke.yarn b/yarns/smoke.yarn
index 2fd3445..a5c2ef2 100644
--- a/yarns/smoke.yarn
+++ b/yarns/smoke.yarn
@@ -642,10 +642,19 @@ knows about. In the future, it will allow manipulaing them as well.
     GIVEN a running Qvarn instance
 
     WHEN client gets an authorization token with scope
-    ... "uapi_resource_types_get"
+    ... "uapi_resource_types_get uapi_resource_types_id_get"
 
     WHEN client requests GET /resource_types using token
     THEN HTTP status code is 200 OK
-    AND search result contains { "id": "/subjects" }
+    AND search result contains { "id": "subject" }
+
+    WHEN client requests GET /resource_types/subject using token
+    THEN HTTP status code is 200 OK
+    AND JSON body matches
+    ... {
+    ...     "id": "subject",
+    ...     "type": "resource_type",
+    ...     "path": "/subjects"
+    ... }
 
     FINALLY qvarn is stopped