Prerequisites for Test Case Execution
This section provides information about the prerequisites that must be achieved in the following sequence before executing test cases:
- Location of the Test Cases
- The Cust-Roaming-Suite directory path is
/var/lib/jenkins/workspace/Regression/Cust-Roaming-Suite
. - The Cust-Core-DSR directory path is
/var/lib/jenkins/workspace/Regression/Cust-Core-DSR
. - The New-Features are located in
/var/lib/jenkins/workspace/New-Features
- The Performance test cases are located in
/var/lib/jenkins/workspace/Performance/Radius_Traffic
- All Cleanup pipeline test cases are located in
/var/lib/jenkins/workspace/Cleanup/Cust-Cleanup-DSR
- The Cust-Roaming-Suite directory path is
- SUT Requirements
Table 3-1 DSR and SDS SUT Details
Server Quantity DSR SUT DSR NOAM Active 1 DSR NOAM Standby 1 DSR Signaling SOAM Active 1 DSR Signaling SOAM Standby 1 DA-MP 2 IPFE 2 SDS SUT SDS NOAM Active 1 SDS NOAM Standby 1 Query Server 1 SDS Signaling SOAM Active 1 SDS Signaling SOAM Standby 1 DP Server 1 Note:
Ensure that when the SUT is created using VNFM, then Mediation, FABR, and RBAR features are enabled. - Update SUT Information in ATS
- Update
/home/cloud-user/Verizon-drop1/dsr-atsV2/dut.yaml
with the SUT details. The same will be automatically copied to the required location when the execution starts from Jenkins. Edit thedut.yaml
file.Update the
dut.yaml
file by referring to the following file:DSRVIP: - name: DSRNOVIP IP: 2606:b400:605:b919:86b8:2ff:fe60:6278 - name: DSRSOVIP IP: 2606:b400:605:b919:86b8:2ff:fe60:62ab SIGNALING_IPs: - IP: 2004:db8:1116::24 type: LocalIp - IP: 2004:db8:1116::e type: LocalIp - IP: 2004:db8:1116::10 type: IpfeTsa - IP: type: IpfeTsa ipfeInitiatorDampIp: - IP: 2004:db8:1116::24 MP_XMI: - IP: 2606:b400:605:b919:86b8:02ff:fe60:629e type: LocalIp - IP: 2606:b400:605:b919:86b8:02ff:fe60:6298 type: LocalIp SDSVIP: - name: SDSNOVIP IP: 2606:b400:605:b919:86b8:2ff:fe60:6295 - name: SDSSOVIP IP: 2606:b400:605:b919:86b8:2ff:fe60:627c - name: SDSQS IP: 2606:b400:605:b919:86b8:02ff:fe60:6242 LOCAL: - SIGNALING_IPs: - 2004:db8:1116::11 - 2004:db8:1116::11 - RERUN_COUNT: 1 SDS_ENABLE: N UI_data: - name: UIData PassWordUI: tekware UserNameUI: guiadmin noamHost: http://[2606:b400:605:b919:86b8:2ff:fe60:6278] soamHost: http://[2606:b400:605:b919:86b8:2ff:fe60:62ab] StandBysoamHost: http://[2606:b400:605:b919:86b8:02ff:fe60:6290] StandBynoamHost: http://[2606:b400:605:b919:86b8:02ff:fe60:628f] sdsnoamHost: http://[2606:b400:605:b919:86b8:2ff:fe60:6295] sdssoamHost: http://[2606:b400:605:b919:86b8:2ff:fe60:627c] StandBysdssoamHost: http://[2606:b400:605:b919:86b8:02ff:fe60:629f] StandBysdsnoamHost: http://[2606:b400:605:b919:86b8:02ff:fe60:62c0]
- Update
/home/cloud-user/Verizon-drop1/dsr-atsV2/auth.yaml
. The same will be automatically copied to the required location when the execution starts from Jenkins. Server credentials, such as username and password, displayed in the following image can be updated if required. - The rerun functionality in the Roaming suite can be
changed by updating the
dut.yaml
file. The values are:- RERUN_COUNT: 1
- SDS_ENABLE: N
- Update
- Enabling the Feature on SUT
Note:
Ensure that there are no backup files in the/var/TKLC/db/filemgmt/backup
location while executing the database restore test case on SOAM. If there are backup files, then the Mediation feature must be enabled in each backup file. Otherwise, sometimes the Mediation feature might get disabled while execution of this test case.- Ensure that RBAR and FABR are enabled as displayed in
the following image:
Figure 3-1 RBAR and FABR Enabled on the DSR GUI
- Ensure that Mediation is enabled as displayed in the
following image:
Figure 3-2 Mediation Enabled on the DSR GUI
- Ensure that DCA is enabled as displayed in the following image:
Figure 3-3 DCA Enabled on the DSR GUI
- Ensure that RBAR and FABR are enabled as displayed in
the following image:
- Configure ComAgent connections on DSR by referring to the
Diameter Signaling Router Cloud Installation Guide.
Note:
The DSR BUG 29035530 can cause ATS GUI case failure due to the "Security Violation" error when you perform any common GUI operation. This can be identified in/var/TKLC/appw/logs/Process/AppWorksGui.log
by searching for the Security violation by a user keyword.