Management, Location, Scheduling & Policies

7 test modules, 249 test cases. ← Back to overview

testMgmtObj.py — All <mgmtObj> specializations (FWR, SWR, MEM, ANI, ANDI, BAT, DVI, DVC, RBO, EVL, NYCFC, etc.) (102 tests)

#	Test Method	Requests Performed
1	test_mgmtObjResourceNameTypeMismatchFail	CREATE a resource using m2m:ae as the JSON key but T.MGMTOBJ as the declared type -> expects BAD_REQUEST.
2	test_mgmtObjResourceNameDefinitionMismatchFail	CREATE a resource using m2m:stor as the JSON key with mgd=23 (wrong mgd for STOR) -> expects BAD_REQUEST.
3	test_mgmtObjMissingMgdFail	CREATE a m2m:stor body under <NOD> with no mgd attribute -> expects BAD_REQUEST.
4	test_mgmtObjWrongMgdFail	CREATE a m2m:stor body with mgd=ANDI (valid but wrong specialization) -> expects BAD_REQUEST.
5	test_createFWR	CREATE a <FWR> (Firmware mgmtObj) under the <NOD> with dc, vr, fwn, url, ud -> expects CREATED; checks ri.
6	test_retrieveFWR	RETRIEVE the <FWR> -> expects OK; checks mgd=FWR.
7	test_attributesFWR	RETRIEVE the <FWR> -> expects OK; checks ty, pi, rn, timestamps, dc, vr, fwn, url, ud, and uds (update status, a dict).
8	test_deleteFWR	DELETE the <FWR> -> expects DELETED.
9	test_createSWR	CREATE a <SWR> (Software) with dc, vr, swn, url -> expects CREATED; checks ri.
10	test_retrieveSWR	RETRIEVE the <SWR> -> expects OK; checks mgd=SWR.
11	test_attributesSWR	RETRIEVE the <SWR> -> expects OK; checks ty, pi, rn, timestamps, dc, vr, swn, url, and presence of in/un/ins (install/uninstall status fields).
12	test_deleteSWR	DELETE the <SWR> -> expects DELETED.
13	test_createMEM	CREATE a <MEM> (Memory) with dc, mma, mmt -> expects CREATED; checks ri.
14	test_retrieveMEM	RETRIEVE the <MEM> -> expects OK; checks mgd=MEM.
15	test_attributesMEM	RETRIEVE the <MEM> -> expects OK; checks ty, pi, rn, timestamps, dc, mma, mmt.
16	test_deleteMEM	DELETE the <MEM> -> expects DELETED.
17	test_createANI	CREATE a <ANI> (areaNwkInfo) with dc, ant, ldv (list) -> expects CREATED; checks ri.
18	test_retrieveANI	RETRIEVE the <ANI> -> expects OK; checks mgd=ANI.
19	test_attributesANI	RETRIEVE the <ANI> -> expects OK; checks ty, pi, rn, timestamps, dc, ant, and ldv (2-item list).
20	test_deleteANI	DELETE the <ANI> -> expects DELETED.
21	test_createANDI	CREATE a <ANDI> (areaNwkDeviceInfo) with dc, dvd, dvt, awi, sli, sld, lnh (list) -> expects CREATED; checks ri.
22	test_retrieveANDI	RETRIEVE the <ANDI> -> expects OK; checks mgd=ANDI.
23	test_attributesANDI	RETRIEVE the <ANDI> -> expects OK; checks ty, pi, rn, timestamps, dc, dvd, dvt, awi, sli, sld, lnh (2-item list).
24	test_deleteANDI	DELETE the <ANDI> -> expects DELETED.
25	test_createBATWrong	CREATE a <BAT> (battery) with an out-of-range bts (battery status, 99) -> expects BAD_REQUEST.
26	test_createBAT	CREATE a <BAT> with valid dc, btl, bts -> expects CREATED; checks ri/ty=MGMTOBJ.
27	test_retrieveBAT	RETRIEVE the <BAT> -> expects OK; checks mgd=BAT.
28	test_attributesBAT	RETRIEVE the <BAT> -> expects OK; checks ty, pi, rn, timestamps, dc, btl, bts.
29	test_deleteBAT	DELETE the <BAT> -> expects DELETED.
30	test_createDVI	CREATE a <DVI> (deviceInfo) with a full set of device-description attributes (dlb, man, mfdl, mfd, mod, smod, dty, dvnm, fwv, swv, hwv, osv, cnty, loc, syst, spur, purl, ptl) -> expects CREATED; checks ri.
31	test_retrieveDVI	RETRIEVE the <DVI> -> expects OK; checks mgd=DVI.
32	test_attributesDVI	RETRIEVE the <DVI> -> expects OK; checks ty, pi, rn, timestamps, and all the device-description attributes match what was created.
33	test_deleteDVI	DELETE the <DVI> -> expects DELETED.
34	test_createDVC	CREATE a <DVC> (deviceCapability) with can, att, cas (action/status dict), cus -> expects CREATED; checks ri.
35	test_retrieveDVC	RETRIEVE the <DVC> -> expects OK; checks mgd=DVC.
36	test_attributesDVC	RETRIEVE the <DVC> -> expects OK; checks ty, pi, rn, timestamps, dc, can, att, cas.acn/cas.sus, cus, and that ena/dis are both true.
37	test_updateDVCEnaTrue	UPDATE the <DVC> setting ena=True -> expects UPDATED; checks ena/dis both still true.
38	test_updateDVCEnaFalse	UPDATE the <DVC> setting ena=False -> expects UPDATED; checks ena/dis both true (CSE resets them).
39	test_updateDVCDisTrue	UPDATE the <DVC> setting dis=True -> expects UPDATED; checks ena/dis both true.
40	test_updateDVCDisFalse	UPDATE the <DVC> setting dis=False -> expects UPDATED; checks ena/dis both true.
41	test_updateDVCEnaDisTrue	UPDATE the <DVC> setting both ena=True and dis=True simultaneously -> expects BAD_REQUEST (mutually exclusive).
42	test_updateDVCEnaDisFalse	UPDATE the <DVC> setting both ena=False and dis=False -> expects UPDATED; checks ena/dis both reset to true.
43	test_deleteDVC	DELETE the <DVC> -> expects DELETED.
44	test_createRBO	CREATE a <RBO> (reboot) with rbo=False, far=False -> expects CREATED; checks ri.
45	test_retrieveRBO	RETRIEVE the <RBO> -> expects OK; checks mgd=RBO.
46	test_attributesRBO	RETRIEVE the <RBO> -> expects OK; checks ty, pi, rn, timestamps, dc, rbo=False, far=False.
47	test_updateRBORboTrue	UPDATE the <RBO> setting rbo=True (trigger reboot) -> expects UPDATED; checks rbo/far both reset to false (action consumed).
48	test_updateRBORboFalse	UPDATE the <RBO> setting rbo=False -> expects UPDATED; checks rbo/far both false.
49	test_updateRBOFarTrue	UPDATE the <RBO> setting far=True (factory reset) -> expects UPDATED; checks rbo/far both reset to false.
50	test_updateRBOFarFalse	UPDATE the <RBO> setting far=False -> expects UPDATED; checks rbo/far both false.
51	test_updateRBORboFarTrue	UPDATE the <RBO> setting both rbo=True and far=True simultaneously -> expects BAD_REQUEST.
52	test_updateRBORboFarFalse	UPDATE the <RBO> setting both rbo=False and far=False -> expects UPDATED; checks both false.
53	test_deleteRBO	DELETE the <RBO> -> expects DELETED.
54	test_createNYCFCwrongSUID	CREATE a <NYCFC> (myCertFileCred) with an invalid suids entry (99) -> expects BAD_REQUEST.
55	test_createNYCFC	CREATE a <NYCFC> with valid suids, mcff, mcfc -> expects CREATED; checks ri.
56	test_retrieveNYCFC	RETRIEVE the <NYCFC> -> expects OK; checks mgd=NYCFC.
57	test_attributesNYCFC	RETRIEVE the <NYCFC> -> expects OK; checks ty, pi, rn, timestamps, dc, suids, mcff, mcfc.
58	test_deleteNYCFC	DELETE the <NYCFC> -> expects DELETED.
59	test_createEVL	CREATE a <EVL> (EventLog) with lgt, lgd, lgst -> expects CREATED; checks ri.
60	test_retrieveEVL	RETRIEVE the <EVL> -> expects OK; checks mgd=EVL.
61	test_attributesEVL	RETRIEVE the <EVL> -> expects OK; checks ty, pi, rn, timestamps, dc, lgt, lgd, lgst, and lga/lgo (action flags) both true.
62	test_deleteEVL	DELETE the <EVL> -> expects DELETED.
63	test_createWIFIC	CREATE a <WIFIC> (wificlient) with ssid, wcrds (credentials dict: enct/unm/pwd), scan=False -> expects CREATED; checks ri.
64	test_retrieveWIFIC	RETRIEVE the <WIFIC> -> expects OK; checks mgd=WIFIC.
65	test_attributesWIFIC	RETRIEVE the <WIFIC> -> expects OK; checks ty, pi, rn, ssid, wcrds.enct/unm/pwd, scan, scanr (empty list), ud, trdst, rdst (all false defaults).
66	test_deleteWIFIC	DELETE the <WIFIC> -> expects DELETED.
67	test_createWIFICCred1Fail	CREATE a <WIFIC> with wcrds.enct=2 combined with unm/pwd (invalid credential-type/field combination) -> expects BAD_REQUEST.
68	test_createWIFICCred2Fail	CREATE a <WIFIC> with wcrds.enct=4 combined with wepk (invalid combination) -> expects BAD_REQUEST.
69	test_createWIFICCred3Fail	CREATE a <WIFIC> with wcrds.enct=8 combined with wpap (invalid combination) -> expects BAD_REQUEST.
70	test_createDATC	CREATE a <DATC> (dataCollection) with cntp (target container path) -> expects CREATED; checks ri.
71	test_updateDATCrpscIntegerFail	UPDATE the <DATC> setting rpsc (report schedule) to a plain integer instead of a schedule-entry list -> expects BAD_REQUEST.
72	test_updateDATCmescIntegerFail	UPDATE the <DATC> setting mesc (measurement schedule) to a plain integer -> expects BAD_REQUEST.
73	test_updateDATCrpscInvalidSchedule1Fail	UPDATE rpsc with a malformed schedule entry (not a dict with sce) -> expects BAD_REQUEST.
74	test_updateDATCrpscInvalidSchedule2Fail	UPDATE rpsc with a sce cron string that has the wrong number of fields (5 instead of 7) -> expects BAD_REQUEST.
75	test_updateDATCrpscValidSchedule	UPDATE rpsc with a valid 7-field cron schedule -> expects UPDATED; checks rpsc is a list.
76	test_updateDATCmescInvalidSchedule1Fail	UPDATE mesc with a malformed schedule entry -> expects BAD_REQUEST.
77	test_updateDATCmescInvalidSchedule2Fail	UPDATE mesc with a wrongly-formatted cron string -> expects BAD_REQUEST.
78	test_updateDATCmescValidSchedule	UPDATE mesc with a valid cron schedule -> expects UPDATED; checks mesc is a list.
79	test_updateDATCmeilWhileMescFail	UPDATE the <DATC> setting meil (measurement interval) while mesc is already set (mutually exclusive) -> expects BAD_REQUEST.
80	test_updateDATCmescMeilFail	UPDATE the <DATC> setting both mesc and meil together in one request -> expects BAD_REQUEST.
81	test_updateDATCremoveMescAddMeil	UPDATE the <DATC> setting mesc=None and meil=10000 together -> expects UPDATED; checks mesc absent and meil set.
82	test_attributesDATC	RETRIEVE the <DATC> -> expects OK; checks ty, pi, rn, cntp, mesc absent, meil=10000, and rpsc has 1 entry with the expected sce.
83	test_deleteDATC	DELETE the <DATC> -> expects DELETED.
84	test_createSIM	CREATE a <SIM> with imsi, icid, sist, sity, spn -> expects CREATED; checks mgd=SIM.
85	test_retrieveSIM	RETRIEVE the <SIM> -> expects OK; checks mgd=SIM.
86	test_attributesSIM	RETRIEVE the <SIM> -> expects OK; checks ty, pi, rn, timestamps, dc, imsi, icid, sist, sity, spn.
87	test_deleteSIM	DELETE the <SIM> -> expects DELETED.
88	test_createMNWK	CREATE a <MNWK> (mobile network info) with cnb, rss, liqu, ipad/ripa (IP address lists), apna, ceid, smnc, smcc, lac, coel -> expects CREATED; checks mgd=MNWK.
89	test_retrieveMNWK	RETRIEVE the <MNWK> -> expects OK; checks mgd=MNWK.
90	test_attributesMNWK	RETRIEVE the <MNWK> -> expects OK; checks ty, pi, rn, timestamps, dc, and all the network attributes (cnb, rss, liqu, ipad/ripa contents, apna, ceid, smnc, smcc, lac, coel).
91	test_deleteMNWK	DELETE the <MNWK> -> expects DELETED.
92	test_createCRDS	CREATE a <CRDS> (credentials) with pur, crid, crse, crtk -> expects CREATED; checks mgd=CRDS.
93	test_retrieveCRDS	RETRIEVE the <CRDS> -> expects OK; checks mgd=CRDS.
94	test_attributesCRDS	RETRIEVE the <CRDS> -> expects OK; checks ty, pi, rn, timestamps, dc, pur, crid, crse, crtk.
95	test_deleteCRDS	DELETE the <CRDS> -> expects DELETED.
96	test_createSTOR	CREATE a <STOR> (Storage mgmtObj) under <NOD> with a full set of storage attributes (uuid, stoTe, wriSd, reaSd, avaSe, totSe, stoPe, sus, nuOMs, nOFUs, filSm, stoNe, mouPt, mouOs, write) -> expects CREATED; checks mgd=STOR and all provided attribute values.
97	test_createSTORWithWrongStoTeFail	CREATE a <STOR> with an out-of-range stoTe=23 -> expects BAD_REQUEST.
98	test_createSTORWithWrongStoPeFail	CREATE a <STOR> with an out-of-range stoPe=23 -> expects BAD_REQUEST.
99	test_createSTORWithWrongSusFail	CREATE a <STOR> with an out-of-range sus=23 -> expects BAD_REQUEST.
100	test_updateSTORformat	CREATE a minimal <STOR> -> expects CREATED; UPDATE setting formt=True (format action) -> expects UPDATED, checks formt=True; DELETE -> expects DELETED.
101	test_updateSTORunmount	CREATE a minimal <STOR> -> expects CREATED; UPDATE setting unmot=True (unmount action) -> expects UPDATED, checks unmot=True; DELETE -> expects DELETED.
102	test_updateSTORformatUnmountFail	CREATE a minimal <STOR> -> expects CREATED; UPDATE setting both formt=True and unmot=True simultaneously (mutually exclusive) -> expects BAD_REQUEST; DELETE -> expects DELETED.

testNOD.py — Node (<NOD>) resource lifecycle and notifications (13 tests)

#	Test Method	Requests Performed
1	test_createNOD	CREATE a <NOD> under the <CSEBase> with a node-ID (ni) -> expects CREATED; checks ri is present.
2	test_retrieveNOD	RETRIEVE the <NOD> -> expects OK.
3	test_retrieveNODWithWrongOriginator	RETRIEVE the <NOD> with an unauthorized originator -> expects ORIGINATOR_HAS_NO_PRIVILEGE.
4	test_attributesNOD	RETRIEVE the <NOD> -> expects OK; checks ty, pi (matches the CSEBase's ri), rn, ct, lt, et, and ni.
5	test_updateNODLbl	UPDATE the <NOD> setting lbl -> expects UPDATED; RETRIEVE it again -> expects OK, checks lbl contains the new tag.
6	test_updateNODUnknownAttribute	UPDATE the <NOD> with an unknown attribute -> expects BAD_REQUEST.
7	test_createAEForNOD	CREATE an <AE> with its nl (node link) pointing to the <NOD> -> expects CREATED, checks nl/ri/aei; RETRIEVE the <NOD> -> expects OK, checks the AE's ri is listed in the node's hael (hosted AE list).
8	test_deleteAEForNOD	DELETE the <AE> -> expects DELETED; RETRIEVE the <NOD> -> expects OK, checks hael is now absent (no more hosted AEs).
9	test_moveAEToNOD2	Re-create the <AE> linked to the first <NOD> (calls test_createAEForNOD); CREATE a 2nd <NOD> -> expects CREATED; UPDATE the <AE> to set nl to the 2nd node -> expects UPDATED, checks nl; RETRIEVE the 1st <NOD> -> expects OK, checks hael is now absent; RETRIEVE the 2nd <NOD> -> expects OK, checks hael now contains the AE's ri.
10	test_deleteNOD2	DELETE the 2nd <NOD> -> expects DELETED; RETRIEVE the <AE> -> expects OK, checks nl is now absent (link removed when its target node was deleted).
11	test_deleteNOD	DELETE the (first) <NOD> -> expects DELETED.
12	test_createNODEmptyHael	CREATE a <NOD> with an explicit empty hael list -> expects BAD_REQUEST.
13	test_createNODDoubleHael	CREATE a <NOD> with a pre-set hael list containing one entry -> expects CREATED, checks hael has length 1; CREATE an <AE> whose nl points to that node -> expects CREATED; RETRIEVE the <NOD> -> expects OK, checks hael still has exactly 1 entry containing the AE's ri (no duplicate); DELETE the <AE> and the <NOD> -> each expects DELETED.

testTGR.py — TriggerRequest (<TGR>) resource functionality (IN-CSE only) (17 tests)

#	Test Method	Requests Performed
1	test_createTGRnoTargetFail	CREATE a <TGR> under the <AE> with tri=42 (no matching <AE> with that tri value exists) -> expects BAD_REQUEST. (IN-CSE only)
2	test_createTGR	CREATE a <TGR> with mei, tri=23 (matching the setUp <AE>), tvt=PT30S -> expects CREATED; checks tst=PROCESSING; DELETE the <TGR> -> expects DELETED. (IN-CSE only)
3	test_createTGRforCRUD	CREATE a <TGR> with tpe=executeCRUD, tiae, tia, tio=CREATE, tirt=AE (a full CRUD-trigger payload) -> expects CREATED; DELETE -> expects DELETED. (IN-CSE only)
4	test_createTGRWithUnknownDomainFail	UPDATE the <AE> setting mei to an unknown domain (42@unknown.domain) -> expects UPDATED; CREATE a <TGR> referencing that mei -> expects CREATED but checks tst=ERROR_NSE_NOT_FOUND (no handler found for that domain); DELETE -> expects DELETED. (IN-CSE only)
5	test_createTGRWithTriggerDelivered	UPDATE the <AE>'s mei to encode the TRIGGER_DELIVERED target status; CREATE a <TGR> -> expects CREATED; sleep; RETRIEVE the <TGR> -> expects OK, checks tst=TRIGGER_DELIVERED; DELETE -> expects DELETED. (IN-CSE only)
6	test_createTGRWithTriggerFailed	Same flow as test_createTGRWithTriggerDelivered but mei encodes TRIGGER_FAILED -> checks tst=TRIGGER_FAILED. (IN-CSE only)
7	test_createTGRWithTriggerReplaced	Same flow but mei encodes TRIGGER_REPLACED -> checks tst=TRIGGER_REPLACED. (IN-CSE only)
8	test_createTGRWithTriggerUnconfirmed	Same flow but mei encodes TRIGGER_UNCONFIRMED -> checks tst=TRIGGER_UNCONFIRMED. (IN-CSE only)
9	test_createTGRWithTriggerExpired	Same flow but mei encodes TRIGGER_EXPIRED and tvt=PT1S (very short timeout) -> checks tst=TRIGGER_EXPIRED. (IN-CSE only)
10	test_updateTGRWithTriggerDelivered	CREATE a <TGR> and wait for TRIGGER_DELIVERED; UPDATE the <TGR> with tpe=registrationRequest (re-trigger) -> expects UPDATED, checks tst=PROCESSING; sleep; RETRIEVE -> checks tst=TRIGGER_DELIVERED; DELETE -> expects DELETED. (IN-CSE only)
11	test_updateTGRWithTriggerFailed	Same CREATE+UPDATE flow but final tst checks TRIGGER_FAILED. (IN-CSE only)
12	test_updateTGRWithTriggerReplaced	Same CREATE+UPDATE flow but final tst checks TRIGGER_REPLACED. (IN-CSE only)
13	test_updateTGRWithTriggerUnconfirmed	Same CREATE+UPDATE flow but final tst checks TRIGGER_UNCONFIRMED. (IN-CSE only)
14	test_updateTGRWithTriggerExpired	Same CREATE+UPDATE flow (with tvt=PT1S) but final tst checks TRIGGER_EXPIRED. (IN-CSE only)
15	test_updateTGRWhileProcessingFail	UPDATE the <AE>'s mei to TRIGGER_DELIVERED; CREATE a <TGR> -> expects CREATED; immediately (without sleeping) UPDATE the <TGR> with a new tpe -> expects UNABLE_TO_REPLACE_REQUEST (still in PROCESSING state); DELETE -> expects DELETED. (IN-CSE only)
16	test_retrieveTGRWhileProcessing	UPDATE the <AE>'s mei to TRIGGER_DELIVERED; CREATE a <TGR> -> expects CREATED; immediately RETRIEVE it -> expects OK, checks tst=PROCESSING; DELETE -> expects DELETED. (IN-CSE only)
17	test_deleteTGRWhileProcessing	UPDATE the <AE>'s mei to TRIGGER_DELIVERED; CREATE a <TGR> -> expects CREATED; immediately DELETE it -> expects DELETED. (IN-CSE only)

testLocation.py — Geo-query functionality and location-based queries (73 tests)

#	Test Method	Requests Performed
1	test_createContainerWrongLocFail	CREATE a <CNT> with loc set to a malformed (non-dict) value -> expects BAD_REQUEST.
2	test_createContainerLocWrongAttributesFail	CREATE a <CNT> with loc containing an unknown sub-attribute (wrong) -> expects BAD_REQUEST.
3	test_createContainerLocPointIntCoordinatesFail	CREATE a <CNT> with loc.typ=1 (Point) and integer (not float) coordinates -> expects BAD_REQUEST.
4	test_createContainerLocPointWrongCountFail	CREATE a <CNT> with loc.typ=1 but multiple coordinate pairs (Point must have exactly one) -> expects BAD_REQUEST.
5	test_createContainerLocPoint	CREATE a <CNT> with a valid loc.typ=1 Point -> expects CREATED, checks loc.typ/crd; DELETE -> expects DELETED.
6	test_createContainerLocLineStringWrongCountFail	CREATE a <CNT> with loc.typ=2 (LineString) but only 1 coordinate pair (needs >=2) -> expects BAD_REQUEST.
7	test_createContainerLocLineString	CREATE a <CNT> with a valid loc.typ=2 LineString (2 points) -> expects CREATED, checks loc.typ/crd; DELETE -> expects DELETED.
8	test_createContainerLocPolygonWrongCountFail	CREATE a <CNT> with loc.typ=3 (Polygon) but only 1 coordinate -> expects BAD_REQUEST.
9	test_createContainerLocPolygonWrongFirstLastCoordinateFail	CREATE a <CNT> with loc.typ=3 whose first and last coordinates don't match (polygon must be closed) -> expects BAD_REQUEST.
10	test_createContainerLocPolygon	CREATE a <CNT> with a valid closed loc.typ=3 Polygon -> expects CREATED, checks loc.typ/crd; DELETE -> expects DELETED.
11	test_createContainerLocMultiPointWrongFail	CREATE a <CNT> with loc.typ=4 (MultiPoint) and a malformed crd -> expects BAD_REQUEST.
12	test_createContainerLocMultiPointWrongCountFail	CREATE a <CNT> with loc.typ=4 and an incorrectly-nested coordinate structure -> expects BAD_REQUEST.
13	test_createContainerLocMultiPoint	CREATE a <CNT> with a valid loc.typ=4 MultiPoint -> expects CREATED, checks loc.typ/crd; DELETE -> expects DELETED.
14	test_createContainerLocMultiLineStringWrongFail	CREATE a <CNT> with loc.typ=5 (MultiLineString) and a malformed crd -> expects BAD_REQUEST.
15	test_createContainerLocMultiLineString2WrongFail	CREATE a <CNT> with loc.typ=5 and an incorrectly-nested crd -> expects BAD_REQUEST.
16	test_createContainerLocMultiLineString	CREATE a <CNT> with a valid loc.typ=5 MultiLineString (2 lines) -> expects CREATED, checks loc.typ/crd; DELETE -> expects DELETED.
17	test_createContainerLocMultiPolygonWrongFail	CREATE a <CNT> with loc.typ=6 (MultiPolygon) and a malformed crd -> expects BAD_REQUEST.
18	test_createContainerLocMultiPolygonWrongFirstLastCoordinateFail	CREATE a <CNT> with loc.typ=6 whose ring isn't closed -> expects BAD_REQUEST.
19	test_createContainerLocMultiPolygon	CREATE a <CNT> with a valid closed loc.typ=6 MultiPolygon -> expects CREATED, checks loc.typ/crd; DELETE -> expects DELETED.
20	test_geoQueryGmtyOnlyFail	RETRIEVE the <AE> with rcn=4 and only gmty (missing gsf/geom) -> expects BAD_REQUEST.
21	test_geoQueryGeomOnlyFail	RETRIEVE with rcn=4 and only geom -> expects BAD_REQUEST.
22	test_geoQueryGsfOnlyFail	RETRIEVE with rcn=4 and only gsf -> expects BAD_REQUEST.
23	test_geoQueryGeomWrongFail	RETRIEVE with rcn=4, gmty=1, gsf=1, and a malformed geom value -> expects BAD_REQUEST.
24	test_geoQueryPointWithinPolygon	CREATE a <CNT> with a Polygon loc; RETRIEVE with a Point geo-query (gsf=1 within) inside the polygon -> expects OK with a match; DELETE -> expects DELETED.
25	test_geoQueryPointOutsidePolygon	Same Polygon <CNT>; geo-query Point outside it (gsf=1) -> expects OK with no match; DELETE -> expects DELETED.
26	test_geoQueryPointWithinPoint	CREATE a <CNT> with a Point loc; geo-query the same Point (gsf=1) -> expects OK with a match; DELETE -> expects DELETED.
27	test_geoQueryPointContainsPoint	Same Point <CNT>; geo-query the same Point with gsf=2 (contains) -> expects OK with a match; DELETE -> expects DELETED.
28	test_geoQueryPointContainsPolygonFail	CREATE a <CNT> with a Polygon loc; geo-query with gsf=2 (contains) against a Point shape -> expects OK with no match (a polygon resource can't be 'contained' the wrong way round); DELETE -> expects DELETED.
29	test_geoQueryPointIntersectsPoint	CREATE a Point <CNT>; geo-query the same Point with gsf=3 (intersects) -> expects OK with a match; DELETE -> expects DELETED.
30	test_geoQueryPointIntersectsPointFail	Same Point <CNT>; geo-query a different, non-intersecting Point (gsf=3) -> expects OK with no match; DELETE -> expects DELETED.
31	test_geoQueryPointIntersectsPolygon	CREATE a Polygon <CNT>; geo-query with a Point inside it (gsf=3) -> expects OK with a match; DELETE -> expects DELETED.
32	test_geoQueryPointIntersectsPolygonFail	Same Polygon <CNT>; geo-query with a Point outside it (gsf=3) -> expects OK with no match; DELETE -> expects DELETED.
33	test_geoQueryLineStringWithinPolygon	CREATE a Polygon <CNT>; geo-query with a LineString fully inside it (gsf=1) -> expects OK with a match; DELETE -> expects DELETED.
34	test_geoQueryLineStringOutsidePolygon	Same Polygon <CNT>; geo-query with a LineString fully outside it (gsf=1) -> expects OK with no match; DELETE -> expects DELETED.
35	test_geoQueryPointWithinLineString1	CREATE a LineString <CNT>; geo-query with a Point on the line (gsf=1) -> expects OK with a match; DELETE -> expects DELETED.
36	test_geoQueryPointWithinLineString2	Same LineString <CNT>; geo-query with a different on-line Point (gsf=1) -> expects OK with a match; DELETE -> expects DELETED.
37	test_geoQueryLineStringContainsLineString	CREATE a LineString <CNT>; geo-query with gsf=2 against a LineString that the resource's geometry contains -> expects OK with a match; DELETE -> expects DELETED.
38	test_geoQueryLineStringContainsPolygonFail	CREATE a Polygon <CNT>; geo-query with gsf=2 against a LineString shape -> expects OK with no match; DELETE -> expects DELETED.
39	test_geoQueryPointIntersectsLineString	CREATE a LineString <CNT>; geo-query with gsf=3 against a Point lying on the line -> expects OK with a match; DELETE -> expects DELETED.
40	test_geoQueryLineStringIntersectsLineString	CREATE a LineString <CNT>; geo-query with gsf=3 against an intersecting LineString -> expects OK with a match; DELETE -> expects DELETED.
41	test_geoQueryLineStringIntersectsLineStringFail	Same LineString <CNT>; geo-query with gsf=3 against a non-intersecting LineString -> expects OK with no match; DELETE -> expects DELETED.
42	test_geoQueryPolygonWithinPolygon	CREATE a Polygon <CNT>; geo-query with gsf=1 against a larger enclosing Polygon -> expects OK with a match; DELETE -> expects DELETED.
43	test_geoQueryPolygonOutsidePolygon	Same Polygon <CNT>; geo-query with gsf=1 against a non-overlapping Polygon -> expects OK with no match; DELETE -> expects DELETED.
44	test_geoQueryPolygonPartlyWithinPolygonFail	CREATE a Polygon <CNT>; geo-query with gsf=1 against a Polygon that only partially overlaps (not fully within) -> expects OK with no match; DELETE -> expects DELETED.
45	test_geoQueryPolygonContainsPolygon	CREATE a larger Polygon <CNT>; geo-query with gsf=2 against a smaller Polygon fully inside it -> expects OK with a match; DELETE -> expects DELETED.
46	test_geoQueryPolygonContainsPolygonFail	Same Polygon <CNT>; geo-query with gsf=2 against a Polygon outside it -> expects OK with no match; DELETE -> expects DELETED.
47	test_geoQueryPolygonIntersectsPolygon	CREATE a Polygon <CNT>; geo-query with gsf=3 against an overlapping Polygon -> expects OK with a match; DELETE -> expects DELETED.
48	test_geoQueryPolygonIntersectsPolygonFail	Same Polygon <CNT>; geo-query with gsf=3 against a non-overlapping Polygon -> expects OK with no match; DELETE -> expects DELETED.
49	test_geoQueryMultiPointWithinPolygon	CREATE a MultiPoint <CNT>; geo-query with gsf=1 against an enclosing Polygon shape -> expects OK with a match; DELETE -> expects DELETED.
50	test_geoQueryMultiPointOutsidePolygon	Same MultiPoint <CNT>; geo-query with gsf=1 against a non-enclosing Polygon -> expects OK with no match; DELETE -> expects DELETED.
51	test_geoQueryMultiPointOutsidePolygonWrongGmtyFail	Same MultiPoint <CNT>; geo-query using a mismatched gmty (Polygon shape type) against an out-of-range query polygon -> expects OK with no match; DELETE -> expects DELETED.
52	test_geoQueryMultiPointContainsPoint	CREATE a MultiPoint <CNT>; geo-query with gsf=2 against one of its own points -> expects OK with a match; DELETE -> expects DELETED.
53	test_geoQueryMultiPointContainsPointFail	Same MultiPoint <CNT>; geo-query with gsf=2 against a Point not in the set -> expects OK with no match; DELETE -> expects DELETED.
54	test_geoQueryPointIntersectsMultiPoint	CREATE a Point <CNT>; geo-query with gsf=3 against a MultiPoint query shape that includes that point -> expects OK with a match; DELETE -> expects DELETED.
55	test_geoQueryPointIntersectsMultiPointFail	Same Point <CNT>; geo-query with gsf=3 against a MultiPoint shape that doesn't include it -> expects OK with no match; DELETE -> expects DELETED.
56	test_geoQueryMultiPointIntersectsMultiPoint	CREATE a MultiPoint <CNT>; geo-query with gsf=3 against an overlapping MultiPoint shape -> expects OK with a match; DELETE -> expects DELETED.
57	test_geoQueryMultiPointIntersectsMultiPointFail	Same MultiPoint <CNT>; geo-query with gsf=3 against a non-overlapping MultiPoint shape -> expects OK with no match; DELETE -> expects DELETED.
58	test_geoQueryMultiLinestringWithinPolygon	CREATE a MultiLineString <CNT>; geo-query with gsf=1 against an enclosing Polygon -> expects OK with a match; DELETE -> expects DELETED.
59	test_geoQueryMultiLinestringOutsidePolygon	Same MultiLineString <CNT>; geo-query with gsf=1 against a non-enclosing Polygon -> expects OK with no match; DELETE -> expects DELETED.
60	test_geoQueryMultiLineContainsPoint	CREATE a MultiLineString <CNT>; geo-query with gsf=2 against a Point on one of its lines -> expects OK with a match; DELETE -> expects DELETED.
61	test_geoQueryMultiLineContainsPointFail	Same MultiLineString <CNT>; geo-query with gsf=2 against a Point not on any line -> expects OK with no match; DELETE -> expects DELETED.
62	test_geoQueryPointIntersectsMultiLine	CREATE a Point <CNT>; geo-query with gsf=3 against a MultiLineString shape it lies on -> expects OK with a match; DELETE -> expects DELETED.
63	test_geoQueryPointIntersectsMultiLineFail	Same Point <CNT>; geo-query with gsf=3 against a MultiLineString it doesn't intersect -> expects OK with no match; DELETE -> expects DELETED.
64	test_geoQueryLineStringIntersectsMultiLine	CREATE a LineString <CNT>; geo-query with gsf=3 against an overlapping MultiLineString -> expects OK with a match; DELETE -> expects DELETED.
65	test_geoQueryLineStringIntersectsMultiLineFail	Same LineString <CNT>; geo-query with gsf=3 against a non-overlapping MultiLineString -> expects OK with no match; DELETE -> expects DELETED.
66	test_geoQueryMultiPolygonWithinPolygon	CREATE a MultiPolygon <CNT>; geo-query with gsf=1 against an enclosing Polygon -> expects OK with a match; DELETE -> expects DELETED.
67	test_geoQueryMultiPolygonOutsidePolygon	Same MultiPolygon <CNT>; geo-query with gsf=1 against a non-enclosing Polygon -> expects OK with no match; DELETE -> expects DELETED.
68	test_geoQueryMultiPolygonContainsPoint	CREATE a MultiPolygon <CNT>; geo-query with gsf=2 against a Point inside one of its polygons -> expects OK with a match; DELETE -> expects DELETED.
69	test_geoQueryMultiPolygonContainsPointFail	Same MultiPolygon <CNT>; geo-query with gsf=2 against a Point outside all polygons -> expects OK with no match; DELETE -> expects DELETED.
70	test_geoQueryPointIntersectsMultiPolygon	CREATE a Point <CNT>; geo-query with gsf=3 against a MultiPolygon shape containing that point -> expects OK with a match; DELETE -> expects DELETED.
71	test_geoQueryPointIntersectsMultiPolygonFail	Same Point <CNT>; geo-query with gsf=3 against a MultiPolygon that doesn't contain it -> expects OK with no match; DELETE -> expects DELETED.
72	test_geoQueryPolygonIntersectsMultiPolygon	CREATE a MultiPolygon <CNT>; geo-query with gsf=3 against an overlapping Polygon -> expects OK with a match; DELETE -> expects DELETED.
73	test_geoQueryPolygonIntersectsMultiPolygonFail	Same MultiPolygon <CNT>; geo-query with gsf=3 against a non-overlapping Polygon -> expects OK with no match; DELETE -> expects DELETED.

testLCP.py — LocationPolicy (<LCP>) resource functionality (17 tests)

#	Test Method	Requests Performed
1	test_createLCPMissingLosFail	CREATE an <LCP> under the <AE> without the mandatory los (location source) attribute -> expects BAD_REQUEST.
2	test_createMinimalLCP	CREATE a minimal <LCP> with only los=2 (device based) -> expects CREATED, checks lost (location status) is empty; DELETE the <LCP> -> expects DELETED.
3	test_createLCPWithSameCNTRnFail	CREATE an <LCP> whose lon (location container name) equals its own resource name -> expects BAD_REQUEST.
4	test_createLCPWithLOS2LotFail	CREATE an <LCP> with los=2 (device based) together with lot (locationTargetID, invalid for that source) -> expects BAD_REQUEST.
5	test_createLCPWithLOS2AidFail	CREATE an <LCP> with los=2 together with aid (authID, invalid for that source) -> expects BAD_REQUEST.
6	test_createLCPWithLOS2LorFail	CREATE an <LCP> with los=2 together with lor (locationServer, invalid for that source) -> expects BAD_REQUEST.
7	test_createLCPWithLOS2RlklFail	CREATE an <LCP> with los=2 together with rlkl=True (retrieveLastKnownLocation, invalid for that source) -> expects BAD_REQUEST.
8	test_createLCPWithLOS2LuecFail	CREATE an <LCP> with los=2 together with luec (locationUpdateEventCriteria, invalid for that source) -> expects BAD_REQUEST.
9	test_createLCPWithWrongGtaFail	CREATE an <LCP> with an invalid gta (geoTargetArea) value -> expects BAD_REQUEST.
10	test_createLCPWithGta	CREATE an <LCP> with a valid GeoJSON polygon as gta -> expects CREATED, checks gta is present; DELETE the <LCP> -> expects DELETED.
11	test_createLCPWithLit2Lou0	CREATE an <LCP> with lit=2 (geo-fence) and lou=['PT0S'] (zero update period) -> expects CREATED, checks lost is empty; DELETE the <LCP> -> expects DELETED.
12	test_testPeriodicUpdates	CREATE an <LCP> geo-fence policy with lou=PT1S (periodic 1s updates), linked container, target polygon, and gec=2 (leaving) -> expects CREATED; CREATE a <CIN> with an outside-the-polygon location -> expects CREATED; sleep; RETRIEVE the linked container's latest <CIN> -> expects OK, checks the geo-fence event code equals 2 (leaving); DELETE the <LCP> -> expects DELETED.
13	test_testManualUpdates	CREATE an <LCP> geo-fence policy with no lou (manual updates) and gec=2 -> expects CREATED; CREATE a <CIN> with an outside location -> expects CREATED; RETRIEVE the latest <CIN> -> expects OK, checks the geo-fence event equals 2 (leaving); DELETE the <LCP> -> expects DELETED.
14	test_testManualInsideEvent	CREATE an <LCP> with gec=3 (inside); feed a sequence of inside/outside <CIN> location updates (inside, inside, outside, outside, inside again) -> each CREATE expects CREATED; after each, RETRIEVE the latest <CIN> -> expects OK and checks the geo-fence event code matches the expected inside/non-inside transitions for each step; DELETE the <LCP> -> expects DELETED.
15	test_testManualOutsideEvent	Same sequence of location updates as the inside-event test but with gec=4 (outside) -> each CREATE/RETRIEVE checks the geo-fence event reflects outside/non-outside transitions correctly at each step; DELETE the <LCP> -> expects DELETED.
16	test_testManualLeavingEvent	Same location-update sequence with gec=2 (leaving) -> checks the leaving event fires only on the inside->outside transition and not otherwise; DELETE the <LCP> -> expects DELETED.
17	test_testManualEnteringEvent	Same location-update sequence with gec=1 (entering) -> checks the entering event fires only on the outside->inside transition and not otherwise; DELETE the <LCP> -> expects DELETED.

testSCH.py — Schedule (<SCH>) resource functionality (22 tests)

#	Test Method	Requests Performed
1	test_createSCHunderCBwithNOCFail	CREATE a <SCH> under <CSEBase> with nco=True (notification congestion, unsupported there) -> expects CONTENTS_UNACCEPTABLE.
2	test_createSCHunderNODwithNOCUnsupportedFail	CREATE a <SCH> under <NOD> with nco=True (unsupported parent type for that feature) -> expects NOT_IMPLEMENTED.
3	test_createSCHunderCBwithoutNCO	CREATE a <SCH> under <CSEBase> without nco, with a schedule expression -> expects CREATED; DELETE it -> expects DELETED.
4	test_updateSCHunderCBwithNCOFail	CREATE a <SCH> under <CSEBase> -> expects CREATED; UPDATE it adding nco=True -> expects CONTENTS_UNACCEPTABLE; DELETE it -> expects DELETED.
5	test_updateSCHunderNODwithNOCUnsupportedFail	CREATE a <SCH> under <NOD> -> expects CREATED; UPDATE it adding nco=True -> expects NOT_IMPLEMENTED; DELETE it -> expects DELETED.
6	test_createSCHunderSUBwrongRn	CREATE a <SUB> -> expects CREATED; CREATE a <SCH> under it with an incorrect, non-standard resource name -> expects BAD_REQUEST; DELETE the <SUB> -> expects DELETED.
7	test_createSCHunderSUBemptyRn	CREATE a <SUB> -> expects CREATED; CREATE a <SCH> under it with no rn -> expects CREATED (default name applied); DELETE the <SUB> -> expects DELETED.
8	test_createSCHunderSUBcorrectRn	CREATE a <SUB> -> expects CREATED; CREATE a <SCH> under it with the correct fixed name notificationSchedule -> expects CREATED; DELETE the <SUB> -> expects DELETED.
9	test_createSCHunderCRSwrongRn	CREATE a <SCH> under the pre-existing <CRS> with an incorrect resource name -> expects BAD_REQUEST.
10	test_createSCHunderCRSemptyRn	CREATE a <SCH> under the <CRS> with no rn -> expects CREATED; DELETE it -> expects DELETED.
11	test_createSCHunderCRScorrectRn	CREATE a <SCH> under the <CRS> with the correct fixed name -> expects CREATED; DELETE it -> expects DELETED.
12	test_createSCHunderCB	CREATE a <SCH> directly under <CSEBase> -> expects CREATED; DELETE it -> expects DELETED.
13	test_createSCHunderCBTwiceFail	CREATE a <SCH> under <CSEBase> -> expects CREATED; CREATE a 2nd one under the same parent -> expects BAD_REQUEST (only one schedule allowed); DELETE the first -> expects DELETED.
14	test_createSCHunderNOD	CREATE a <SCH> under <NOD> -> expects CREATED; DELETE it -> expects DELETED.
15	test_testSCHunderSUBinsideSchedule	CREATE a <SUB> -> expects CREATED; CREATE a <SCH> under it with a schedule window starting soon -> expects CREATED; UPDATE the <AE> to trigger a notification -> expects UPDATED; checks a notification IS received once inside the scheduled window; DELETE the <SUB> -> expects DELETED.
16	test_testSCHunderSUBoutsideSchedule	Same setup but the schedule window starts later (outside the immediate check window) -> UPDATE the <AE> -> expects UPDATED; checks NO notification is received yet; DELETE the <SUB> -> expects DELETED.
17	test_testSCHunderSUBoutsideScheduleImmediate	Same out-of-window schedule but the <SUB> has nec=2 (immediate notification, bypassing schedule) -> UPDATE the <AE> -> expects UPDATED; checks a notification IS received immediately despite being outside the schedule; DELETE the <SUB> -> expects DELETED.
18	test_testSCHunderSUBWithOMinsideSchedule	CREATE a <SUB> with an om (operationMonitor) on RETRIEVE -> expects CREATED; CREATE a <SCH> with an immediate window -> expects CREATED; RETRIEVE the <AE> (the monitored operation) -> expects OK; checks a notification is received inside the schedule; DELETE the <SUB> -> expects DELETED.
19	test_testSCHunderSUBWithOMoutsideSchedule	Same operationMonitor <SUB> but with a later schedule window -> RETRIEVE the <AE> -> expects OK; checks NO notification yet; DELETE the <SUB> -> expects DELETED.
20	test_testSCHunderSUBWithOMoutsideScheduleImmediate	Same as above but nec=2 (immediate) on the <SUB> -> RETRIEVE the <AE> -> expects OK; checks a notification IS received immediately despite the later schedule; DELETE the <SUB> -> expects DELETED.
21	test_testSCHunderCRSinsideSchedule	CREATE a <CRS> (cross-resource subscription monitoring the <AE>) -> expects CREATED; CREATE a <SCH> under it with an immediate window -> expects CREATED; UPDATE the <AE> to trigger evaluation -> expects UPDATED; checks a notification IS received inside the window; DELETE the <CRS> -> expects DELETED.
22	test_testSCHunderCRSoutsideScheduleFail	Same <CRS> setup but the <SCH> window starts later -> UPDATE the <AE> -> expects UPDATED; checks NO notification is received (outside the schedule); DELETE the <CRS> -> expects DELETED.

testPDR.py — PolicyDeletionRules resource functionality (5 tests)

#	Test Method	Requests Performed
1	test_createPDR	CREATE a <PDR> under the <NTP> (created in setUp) -> expects CREATED.
2	test_retrievePDR	RETRIEVE the <PDR> -> expects OK.
3	test_updatePDR	UPDATE the <PDR> setting lbl -> expects UPDATED; checks the returned lbl matches.
4	test_deletePDR	DELETE the <PDR> -> expects DELETED.
5	test_createTooManyPDRsFail	CREATE 2 additional <PDR>s under the <NTP> in a loop -> each expects CREATED; CREATE a 3rd <PDR> -> expects CONFLICT (exceeds the maximum allowed PDRs per NTP); DELETE the 2 created <PDR>s -> each expects DELETED.