WARNING! Gitlab maintenance operation scheduled for Monday, 20 April between 12:00 and 14:00 (CET). During this time window, short service interruptions (less than 5 minutes) may occur. Thank you in advance for your understanding.
# Check that a VBS in VRU-ACTIVE-STANDALONE stops the transmission of VAMs when changing to VRU-IDLE
# Check that a VBS in VRU-ACTIVE-STANDALONE stops the transmission of VAMs when changing to VRU-IDLE
#ItsVru_TestCases.TC_VBS_CLTR_BV_03
#ItsVru_TestCases.TC_VBS_CLTR_BV_03
# Check that a cluster breaking VRU stops sending cluster VAMs
# Check that a cluster breaking VRU stops sending cluster VAMs
#ItsVru_TestCases.TC_VBS_CLTR_BV_04
ItsVru_TestCases.TC_VBS_CLTR_BV_04
# Check that a VRU sends an indication of joining a cluster for timeClusterJoinNotification including the identified cluster and time at which it stops sending individual VAMs
# Check that a VRU sends an indication of joining a cluster for timeClusterJoinNotification including the identified cluster and time at which it stops sending individual VAMs
#ItsVru_TestCases.TC_VBS_CLTR_BV_05
#ItsVru_TestCases.TC_VBS_CLTR_BV_05
# Check that a VBS sends individual VAMs after a cancelled-join oder failed-join including the same station ID as before and the cluster leave notification for timeClusterLeaveNotification
# Check that a VBS sends individual VAMs after a cancelled-join oder failed-join including the same station ID as before and the cluster leave notification for timeClusterLeaveNotification
# Check that a cluster leader indicates a cluster ID change for timeClusterIdChangeNotification before the change
# Check that a cluster leader indicates a cluster ID change for timeClusterIdChangeNotification before the change
#ItsVru_TestCases.TC_VBS_CLTR_BV_09
#ItsVru_TestCases.TC_VBS_CLTR_BV_09
# Check that a cluster leader sends a cluster VAM with the new ID as soon as possible
# Check that a cluster leader sends a cluster VAM with the new ID as soon as possible
#ItsVru_TestCases.TC_VBS_CLTR_BV_10()
#ItsVru_TestCases.TC_VBS_CLTR_BV_10
# Check that a VBS starts sending VAMs when the state changes from VRU-IDLE to VRU-ACTIVE-STANDALONE
#ItsVru_TestCases.TC_VBS_CLTR_BV_01
# Check that the cluster size is set to minClusterSize and the VRU profile field is set to the VRU profile
#ItsVru_TestCases.TC_VBS_CLTR_BV_02
# Check that the minimum time elapsed between the start of consecutive VAM generation events is equal or larger than T_Gen_Vam
#ItsVru_TestCases.TC_VBS_FRPE_TI_04
# Check that T_GenVam is set to T_GenVamMin if the value for T_GenVam is not provided by the VBS management entity or smaller than T_GenVamMin in case of ITS-G5
#ItsVru_TestCases.TC_VBS_FRPE_TI_05
# Check that the minimum time elapsed between the start of consecutive VAM generation events is equal or larger than T_Gen_Vam
#ItsVru_TestCases.TC_VBS_FRPE_TI_01 runs on ItsVru system ItsVruSystem {
# Check that the LF container is included in the first VAM generation
#ItsVru_TestCases.TC_VBS_FRPE_BV_02
# Check that the LF container is included periodically after 2000 ms
#ItsVru_TestCases.TC_VBS_FRPE_BV_03
# Check that the ITS-AID indicates the application for which permissions are being granted
# Check that the ITS-AID indicates the application for which permissions are being granted