Fixed Failed-AVP bug (feature). Now wrong avps inside grouped are correctly tracked

[anna.git] / example / diameter / launcher / resources / ft-client / tests / experiment2 / ProtocolErrors / BadAARtoServer / case_3.tc

diff --git a/example/diameter/launcher/resources/ft-client/tests/experiment2/ProtocolErrors/BadAARtoServer/case_3.tc b/example/diameter/launcher/resources/ft-client/tests/experiment2/ProtocolErrors/BadAARtoServer/case_3.tc
index f1fdf40..06b5efc 100644 (file)
--- a/example/diameter/launcher/resources/ft-client/tests/experiment2/ProtocolErrors/BadAARtoServer/case_3.tc
+++ b/example/diameter/launcher/resources/ft-client/tests/experiment2/ProtocolErrors/BadAARtoServer/case_3.tc
@@ -8,6 +8,4 @@ WAIT4MESSAGE
 
 # Check Failed-AVP & Subscription-Id within:
 CHECKPATTERN <avp name="Result-Code" data="5004" alias="DIAMETER_INVALID_AVP_VALUE"/>
-CHECKPATTERN <avp name="Failed-AVP">( *)<avp name="Media-Component-Description"
-
-# TODO: check that the complete hierarchy to Flow-Status (the real bad avp)
+CHECKPATTERN <avp name="Failed-AVP">( *)<avp name="Media-Component-Description">( *)<avp name="Media-Sub-Component">( *)<avp name="Flow-Status" data="0" alias="ENABLED-UPLINK"/>