Commit a66ce21c authored by Michele Carignani's avatar Michele Carignani
Browse files

revised second TP of MEC 011

parent 3e912294

Test Purposes/MEC011/mec-011-domain.tplan2

+5 −2
Original line number Diff line number Diff line
@@ -2,12 +2,14 @@ Package MEC_011_Domain { 
	

	Domain {

		pics:

		- PIC_MEC_PLAT

		- PIC_SERVICES

		- PIC_MEC_PLAT // FUT is a MEC Platform

		- PIC_SERVICES // Implements services

		- PIC_NOTIFICATIONS // Implements notifications

		;

		entities:

		- MEC_APP	// MEC Application using the MEC Platform Application Enablement API

		- IUT		// MEC Platform

		- TestSystem

		;

		events:

		- services_running		// services available in the IUT
@@ -18,6 +20,7 @@ Package MEC_011_Domain { 
		- sends					// IUT sends an HTTP response

		- being_in

		- idle_state // Idle state: The MEC platform has services running and MEC Application is authorized to consume services

		- subscribed_to

		;

	}

Test Purposes/MEC011/mec-011.tplan2

+11 −49
Original line number Diff line number Diff line
@@ -61,46 +61,31 @@ Package MEC_011_mp1 { 
	}





	





	Test Purpose {

		TP Id "TP/MEC/PLATFORM/API/SERVICES/002"

		

		/* Q:

		this is testing for 5.2.4 (service registration/update plus notification to other APPs) 

		but the reference is for  7.4.3.4 (service registration/update only).

		What shall be the scope of the test?

		*/

		TP Id "TP_MEC_PLAT_MP1_SAQ_BV_002" // SAQ = Service Availability Query

		

		Test objective 

			"Check that the IUT notifies the authorised relevant application instances 

			when a new service is registered or updated"

			when a new service is registered or updated when they are subscribed"

		

		Reference "ETSI GS MEC 011 V2.0.3, clause 7.4.3.4"

 		PICS Selection PIC_MEC_PLAT		// Q: do we need a different one?

 		PICS Selection PIC_MEC_PLAT PIC_SERVICES PIC_NOTIFICATIONS



		/* Q:

		should we have different APPs that won't get the notification because they  

		aren't registered for the service (for better test coverage and accuracy)?

		*/

		Initial conditions  with {

			the IUT entity having services_running

			and the IUT entity having started the MEC_APP entity

			and the MEC_APP is authorized to consume_services

			the IUT entity being_in idle_state and

			the TestSystem entity subscribed_to the MP1_Notifications

		}



		Expected behaviour

		    ensure that {

		        when {

		        	// Q: should the parameters be done in a configuration (Data/Configuration like in lis.tplsan2 example)?

		            the IUT entity receives a POST containing

		                Uri indicating value "/mp1/v1/services",	// Q: how to define the query parameter?

		                Host,

		                Content_type indicating value "application/json;charset=utf-8",		// Q: is the content type defined anywhere?

		                Uri indicating value "/mp1/v1/services",

		                Host indicating value IUT_HOSTNAME,

		                Content_type indicating value "application/json;charset=utf-8"		// Q: is the content type defined anywhere?

		                // Q: how to ensure HTTPS, OAuth 2.0 with bearer tokens (clause 7.2)

		                ;

		            ;

		            //;

		        }

		        then {

		            the IUT entity sends a httpResponse containing
@@ -109,31 +94,8 @@ Package MEC_011_mp1 { 
		                version indicating value "1.0",		// Q: do we only accept a specific version?

		                Content_type indicating value "application/json;charset=utf-8",

		                body containing

		                	// Taken from an example

		                	// Are we going to use this verbose format or using mappable test data as per 'TDL Tutorial.pdf, slide 12'? 

		                    xmlMessage containing

		                        version indicating value "1.0",

		                        element "locationResponse" inNamespace "urn:ietf:params:xml:ns:geopriv:held" containing

		                            element "presence" inNamespace "urn:ietf:params:xml:ns:pidf" containing

		                                attribute "entity" indicating value valid "pres:" uri,

		                                element "tuple" containing

		                                    attribute "id",

		                                    element "status" containing

		                                        element "geopriv" inNamespace "urn:ietf:params:xml:ns:pidf:geopriv10" containing

		                                            element "location-info" containing

		                                                element "Point" inNamespace "http://www.opengis.net/gml" containing

		                                                    attribute "srsName" indicating value "urn:ogc:def:crs:EPSG::4326",

		                                                    element "pos" indicating value POINT_POS

		                                                ;

		                                            ;

		                                        ;

		                                    ;

		                                ;

		                            ;

		                        ;

		                    ;

		                ;

		            ;

		                	something indicating value lol

		            ;;

		        }

		}

	}

Test Purposes/MEC011/mec-011.tplan2.docx

0 → 100644
+12.1 KiB

File added.

No diff preview for this file type.

View file

Test Purposes/MEC011/~$c-011.tplan2.docx

0 → 100644
+162 B

File added.

No diff preview for this file type.

View file