Loading mwt-examples/src/tdl/Descriptions.tdltx +52 −4 Original line number Original line Diff line number Diff line Loading @@ -7,11 +7,54 @@ Package Descriptions { Import all from HTTP.MessageBased Import all from HTTP.MessageBased Annotation Failure Annotation Failure Type ^PICS extends Boolean PICS xxx ^PICS MW_8040 //introduce dedicated type that extends boolean? ^PICS MW_8345 // Type ^PICS extends Boolean // PICS MW_8040 // PICS MW_8345 //or just annotated booleans? (probably more consistent): @PICS Boolean MW_8040 @PICS Boolean MW_8345 //TODO: add constraints for PICS guards? //TODO: make PICS a sub-type of simple data instance? Use "settings" as settings Map MW_8040 to "pics.mw_8040" in settings as MW_8040_MAPPING Map MW_8345 to "pics.mw_8345" in settings as MW_8345_MAPPING Boolean TD_SSP_01_Completed Boolean TD_SSP_01_Completed PICS MW_8345x Test Purpose tpName { Objective: "description" Reference: "reference" PICS: MW_8345x and MW_8345x } //import //@PICSs [ (MW_8040 or MW_8345) ] for testDescriptionName Test Description testDescriptionName uses TestLanArchitecture // if [ (MW_8040 or MW_8345) ] { // pm::mpi sends rGET() to X::mpi // // } //TODO: annotation of behaviour or of block? (block in TPD) //-> syntactically not possible to annotate block at the moment //-> even with exception, still assigned to behaviour //-> moved inside guard // @PICS [ @PICS (MW_8040 or MW_8345) ] //if not true -> verdict N/A? test not executed { @Initial conditions { //-> aka preamble (postamble for final conditions) //if unexpected -> verdict inconclusive, map to junit annotations pm::mpi sends rGET() to X::mpi } //... } String modules_state_uri String modules_state_uri Use "pm.settings.json" as SETTINGS Use "pm.settings.json" as SETTINGS Loading Loading @@ -57,7 +100,12 @@ Package Descriptions { Objective: TD_MDD_01 Objective: TD_MDD_01 Configuration: TestLanArchitecture //TREE_CFG? Configuration: TestLanArchitecture //TREE_CFG? PICS: (MW_8040 or MW_8345) //etc. PICS: (MW_8040 or MW_8345) //etc. //TODO: add annotation to guard/expression to distinguish from regular guards? //->turn PICS keyword into a annotation? Initial conditions Initial conditions //TODO: do we need different semantics for unexpected behaviour within initial/final conditions? //e.g. inconclusive instead of fail? //->in case describe in part 4/1 with { with { //initial textual //initial textual perform action: "Postman has been correctly initialized earlier, by executing perform action: "Postman has been correctly initialized earlier, by executing Loading mwt-examples/src/tdl/Descriptions.tdltx.tdltx 0 → 100644 +0 −0 Empty file added. mwt-examples/src/tdl/Standard.tdltx +8 −7 Original line number Original line Diff line number Diff line Loading @@ -35,6 +35,7 @@ Package Standard { Annotation Test Purpose Description Annotation Test Purpose Description Annotation when Annotation when Annotation then Annotation then Annotation PICS Predefined == returns Boolean Predefined == returns Boolean Predefined != returns Boolean Predefined != returns Boolean Loading Loading
mwt-examples/src/tdl/Descriptions.tdltx +52 −4 Original line number Original line Diff line number Diff line Loading @@ -7,11 +7,54 @@ Package Descriptions { Import all from HTTP.MessageBased Import all from HTTP.MessageBased Annotation Failure Annotation Failure Type ^PICS extends Boolean PICS xxx ^PICS MW_8040 //introduce dedicated type that extends boolean? ^PICS MW_8345 // Type ^PICS extends Boolean // PICS MW_8040 // PICS MW_8345 //or just annotated booleans? (probably more consistent): @PICS Boolean MW_8040 @PICS Boolean MW_8345 //TODO: add constraints for PICS guards? //TODO: make PICS a sub-type of simple data instance? Use "settings" as settings Map MW_8040 to "pics.mw_8040" in settings as MW_8040_MAPPING Map MW_8345 to "pics.mw_8345" in settings as MW_8345_MAPPING Boolean TD_SSP_01_Completed Boolean TD_SSP_01_Completed PICS MW_8345x Test Purpose tpName { Objective: "description" Reference: "reference" PICS: MW_8345x and MW_8345x } //import //@PICSs [ (MW_8040 or MW_8345) ] for testDescriptionName Test Description testDescriptionName uses TestLanArchitecture // if [ (MW_8040 or MW_8345) ] { // pm::mpi sends rGET() to X::mpi // // } //TODO: annotation of behaviour or of block? (block in TPD) //-> syntactically not possible to annotate block at the moment //-> even with exception, still assigned to behaviour //-> moved inside guard // @PICS [ @PICS (MW_8040 or MW_8345) ] //if not true -> verdict N/A? test not executed { @Initial conditions { //-> aka preamble (postamble for final conditions) //if unexpected -> verdict inconclusive, map to junit annotations pm::mpi sends rGET() to X::mpi } //... } String modules_state_uri String modules_state_uri Use "pm.settings.json" as SETTINGS Use "pm.settings.json" as SETTINGS Loading Loading @@ -57,7 +100,12 @@ Package Descriptions { Objective: TD_MDD_01 Objective: TD_MDD_01 Configuration: TestLanArchitecture //TREE_CFG? Configuration: TestLanArchitecture //TREE_CFG? PICS: (MW_8040 or MW_8345) //etc. PICS: (MW_8040 or MW_8345) //etc. //TODO: add annotation to guard/expression to distinguish from regular guards? //->turn PICS keyword into a annotation? Initial conditions Initial conditions //TODO: do we need different semantics for unexpected behaviour within initial/final conditions? //e.g. inconclusive instead of fail? //->in case describe in part 4/1 with { with { //initial textual //initial textual perform action: "Postman has been correctly initialized earlier, by executing perform action: "Postman has been correctly initialized earlier, by executing Loading
mwt-examples/src/tdl/Standard.tdltx +8 −7 Original line number Original line Diff line number Diff line Loading @@ -35,6 +35,7 @@ Package Standard { Annotation Test Purpose Description Annotation Test Purpose Description Annotation when Annotation when Annotation then Annotation then Annotation PICS Predefined == returns Boolean Predefined == returns Boolean Predefined != returns Boolean Predefined != returns Boolean Loading
