Skip to content

default ptp profile test description · Changes

Page history
Update default ptp profile test description authored by Maciej Lipinski's avatar Maciej Lipinski
Hide whitespace changes
Inline Side-by-side
default-ptp-profile-test-description.md
View page @ 3a56fe9a
......@@ -91,22 +91,22 @@ The tests that we expect the WR Switch to pass are listed below. There is a numb
## Test that do not pass because of known bugs (5 tests)
| TEST Name | Test Descrition |
| --------- | ------ |
|MHG_012|Verify that the boundary clock transmits Delay_Resp message as unicast on reception of unicast Delay_Req messages.|
|MTG_011|Verify that boundary clock configured for unicast transmission shall send follow_up message to same unicast address as the associated sync|
|PCG_002|Verify that the boundary clock supports to configure domain number to any value in range 0 to 127.|
|PCG_003|Verify that the boundary clock configured for unicast transmission in Master has the unicastFlag field as TRUE in Delay Request-Response|
|PCG_004|Verify that the boundary clock configured for unicast transmission has the unicastFlag field as TRUE in Peer Delay messages.|
|PCG_007|Verify that the boundary clock configured for One-Step clock has the twoStepFlag field as FALSE in all Sync messages.|
|PCG_008|Verify that the boundary clock configured for One-Step clock has the twoStepFlag field as FALSE in Pdelay_Resp messages.|
|PCG_011|Verify that the boundary clock supports to configure priority1 to any value in range 0-255.|
|PCG_013|Verify that the boundary clock does not allows to configure it as a Slave-only clock.|
|PCG_014|Verify that the DUT transmits announce message with logMessageInterval field which matches it's configured Announce Interval.|
|PCG_015|Verify that the DUT transmits multicast sync/ Sync and Follow_up message with logMessageInterval field which matches it's configured sync|
|PCG_016|Verify that the DUT transmits unicast sync/ sync and follow_up message with logMessageInterval field as 7F.|
|PCG_017|Verify that the boundary clock configured for unicast transmission in Slave has the unicastFlag field as TRUE in Delay Request message.|
|SMG_017|Verify that the boundary clock in FAULTY state moves to the LISTENING state when the fault is cleared.|
| TEST Name | Test Descrition | Comment |
| --------- | ------ | ------ |
|MHG_012|Verify that the boundary clock transmits Delay_Resp message as unicast on reception of unicast Delay_Req messages.| Unicast not implemented. |
|MTG_011|Verify that boundary clock configured for unicast transmission shall send follow_up message to same unicast address as the associated sync.| Unicast not implemented. |
|PCG_002|Verify that the boundary clock supports to configure domain number to any value in range 0 to 127.| Requires implementation of dynamic re-configuration. When we attempt to configure -1 as the domain number, DUT reverts to its default config and transmits Announce message with Domain number as 255 instead of retaining the domain number as 127 (the previous domain number configured by the test case). |
|PCG_003|Verify that the boundary clock configured for unicast transmission in Master has the unicastFlag field as TRUE in Delay Request-Response| Unicast not implemented. |
|PCG_004|Verify that the boundary clock configured for unicast transmission has the unicastFlag field as TRUE in Peer Delay messages.| Unicast not implemented. |
|PCG_007|Verify that the boundary clock configured for One-Step clock has the twoStepFlag field as FALSE in all Sync messages.| One-step configuration not supported/implemented |
|PCG_008|Verify that the boundary clock configured for One-Step clock has the twoStepFlag field as FALSE in Pdelay_Resp messages.| One-step configuration not supported/implemented |
|PCG_011|Verify that the boundary clock supports to configure priority1 to any value in range 0-255.| Requires implementation of dynamic re-configuration.When we attempt to configure 256 as priority1, DUT reverts to its default config and transmits Announce message with priority1 as 0 instead of retaining the domain number as 255 (the previous priority1 value configured by the test case) |
|PCG_013|Verify that the boundary clock does not allows to configure it as a Slave-only clock.| Requires implementation of dynamic re-configuration.|
|PCG_014|Verify that the DUT transmits announce message with logMessageInterval field which matches it's configured Announce Interval.| Requires implementation of dynamic re-configuration. When we attempt to configure -1 as Announce Interval, DUT reverts to its default config and transmits Announce message with logMessageInterval as 0 instead of retaining the logMessageInterval as 4 (the previous logMessageInterval value configured by the test case)|
|PCG_015| Verify that the DUT transmits multicast sync/ Sync and Follow_up message with logMessageInterval field which matches it's configured sync |Requires implementation of dynamic re-configuration.|
|PCG_016|Verify that the DUT transmits unicast sync/ sync and follow_up message with logMessageInterval field as 7F.| Unicast not implemented. |
|PCG_017|Verify that the boundary clock configured for unicast transmission in Slave has the unicastFlag field as TRUE in Delay Request message.|Unicast not implemented. |
|SMG_017|Verify that the boundary clock in FAULTY state moves to the LISTENING state when the fault is cleared.| To be investigated.|
## Historical data
......