Groovy clean tests clean-up

- test labels are modified to set standards for writing tests
   - labels are not expected to be technical
   - labels need to be in simple language that ANYONE can understand
   - labels should not have exact method names except for some mocking
- variables are modified to give highlight to ONLY important parameter of test
   - wild cards are preferred when possible i.e. for exception cases

Issue-ID: CPS-588
Signed-off-by: emaclee <lee.anjella.macabuhay@est.tech>
Change-Id: I3d42471e7aa4bc61f962ad19cc1f237f6985a9a2

1 files changed, 17 insertions, 0 deletions

diff --git a/src/test/resources/moduleResources.json b/src/test/resources/moduleResources.json
new file mode 100644
index 00000000..57f5aefd
--- /dev/null
+++ b/src/test/resources/moduleResources.json
@@ -0,0 +1,17 @@
+{
+  "data": {
+    "modules": [
+      {
+        "name": "ietf-yang-library",
+        "revision": "2016-06-21"
+      },
+      {
+        "name": "nc-notifications",
+        "revision": "2008-07-14"
+      }
+    ]
+  },
+  "cmHandleProperties": {
+    "subsystemId": "system-001"
+  }
+}