Open APIs

 View Only
Back to discussions
Expand all | Collapse all

[TMF653 & 769] TestMeasureDefinition & TestMeasure

  • 1.  [TMF653 & 769] TestMeasureDefinition & TestMeasure

    TM Forum Member
    Posted Aug 07, 2024 13:37

    Hi community,

    We are currently implementing TMF653 (Service Test Mgt) & TMF769 (Product Test Mgt) and we are struggling with the intended usage of TestMeasureDefinition in Service/ProductTestSpecification vs TestMeasure in Service/ProductTest

    Let me elaborate:

    * ServiceTest & ProductTest have

    • 0..* Characteristic = "List of characteristics with values that define the test run"
    • 0..* TestMeasure = "The results of the test in terms of the measured metrics"
    • and TestMeasure in turn has 0..1 Characteristic as value of the test measure 

    * ServiceTestSpecification & ProductTestSpecification have

    • 0..* CharacteristicSpecification = "List of characteristics that the entity can take" (entity here = ServiceTest & ProductTest)
    • 0..* TestMeasureDefinition = "A list of definitions for the measurements for the test defined by this specification"

    The intention seems pretty clear:

    • use Test.characteristic as "input" to define the test run
    • use  Test.testMeasure and TestMeasure.value for the results of the test run

    Now to the question on specifying the 1) test run parameters and 2) the test run results (TestMeasure.value: Characteristic)

    1) is obvious = use TestSpecification to specify the supported characteristics as CharacteristicSpefication (standard spec pattern)

    2) is less obvious:

    • at first glance, TestMeasureDefinition should be used to defined allowed TestMeasure
    • TestMeasureDefinition allows to define the metric (metricName, metricDescription, metricHref) which is also referenced in TestMeasure
      • one could assume that the Metric defines the supported results as CharacteristicSpecification to be used in TestMeasure, but there is no managed resource called Metric (at least I did not find it ...)
      • another assumption could be that TestMeasureDefinition defines the supported results as CharacteristicSpecification to fall back on the standard Spec pattern, but TestMeasureDefinition does not have any CharacteristicSpecification 

    That is the problem we are struggling with = what is the intended way to define, in the TestSpec, the supported test results (TestMeasure.value: Characteristic)  

    Can anyone help on what the intention in those APIs is?

    Thanks a lot, Iwan 



    ------------------------------
    Iwan Gramatikoff
    Edelweiss Service Consulting SàRL
    ------------------------------