Sno TestCase ID Pre Condition

TC-SCJRP-001

1) Schedule Job run Property value in the

NetKNow Properties file should be set to
15 Mins

TC-SCJRP-002

1) Schedule Job run Property value in the

NetKNow Properties file should be set to
15 Mins

TC-SCJRP-003

1) Schedule Job run Property value in the

NetKNow Properties file should be set to
15 Mins

TC-SCJRP-004

1) Schedule Job run Property value in the

NetKNow Properties file should be set to
TC-SCJRP-005 15 Mins

1) Schedule Job run Property value in the

NetKNow Properties file should be set to
15 Mins
TC-SCJRP-006

1) Schedule Job run Property value in the

NetKNow Properties file should be set to
15 Mins
TC-SCJRP-007
 1) Schedule Job run Property value in the
NetKNow Properties file should be set to
15 Mins
TC-SCJRP-008

1) Schedule Job run Property value in the

NetKNow Properties file should be set to
15 Mins
TC-SCJRP-009

1) Schedule Job run Property value in the

NetKNow Properties file should be set to
15 Mins
TC-SCJRP-010

1) Schedule Job run Property value in the

NetKNow Properties file should be set to 5
Mins

TC-SCJRP-011

1) Schedule Job run Property value in the

NetKNow Properties file should be set to 5
Mins

TC-SCJRP-012

1) Schedule Job run Property value in the

NetKNow Properties file should be set to
10 Mins from previous 5 Mins value
2) Do Not restart the Tomcat
TC-SCJRP-014
 1) Schedule Job run Property value in the
NetKNow Properties file should be set to
10 Mins from previous 5 Mins value
2) Do Not restart the Tomcat
TC-SCJRP-015

1) Schedule Job run Property value in the

NetKNow Properties file should be set to
10 Mins from previous 5 Mins value
TC-SCJRP-016 2) Do Not restart the Tomcat

1) Schedule Job run Property value in the

NetKNow Properties file should be set to
10 Mins from previous 5 Mins value
TC-SCJRP-017 2) Do Not restart the Tomcat

1) Schedule Job run Property value in the

NetKNow Properties file should be set to
10 Mins
TC-SCJRP-018 2) Do Not restart the Tomcat

1) Schedule Job run Property value in the

NetKNow Properties file should be set to
10 Mins

TC-SCJRP-019
 Test Case Description
General Positive Cases
To verify that schedule Job property exists in
NetKnow.Properties file for setting the time

To verify that the scheduler job will report the information

about the NetKnow Provision service status for every 'x' time
that is set for Schedule Job property value in NetKNow
properties file

To verify that the scheduler job will report the information

about the Netknow Order service status for every 'x' time that
is set for Schedule Job property value in NetKNow properties
file

To verify that the scheduler job will report the information

about the Netknow Core service status for every 'x' time that
is set for Schedule Job property value in NetKNow properties
file

To verify that the scheduler job will report the information

about the ITPAM status for every 'x' time that is set for
Schedule Job property value in NetKNow properties file

To verify that the scheduler job will report the information

about the Kore Database status for every 'x' time that is set for
Schedule Job property value in NetKNow properties file

To verify that the scheduler job will report the information

about the Kore Transaction status for every 'x' time that is set
for Schedule Job property value in NetKNow properties file
To verify that the scheduler job will report the information
about the CAPC status for every 'x' time that is set for
Schedule Job property value in NetKNow properties file

To verify that the scheduler job will report the information

about the NFA status for every 'x' time that is set for Schedule
Job property value in NetKNow properties file

To verify that the scheduler job will report the information

about the NAT status for every 'x' time that is set for Schedule
Job property value in NetKNow properties file

Miscellaneous
To verify that the scheduler job will not report the information
about any service that is up/down when the scheduler service
itself is down

To verify that the scheduler job will report the information

about more than one service which is down when the
scheduler job runs at configured 'x' time

To verify that the updates to scheduler job run property in

netknow.properties file do not require restart for reporting
any service status in logs
To verify that the scheduler job will report the information
about more than one CAPC's down after the configured 'x'
time

To verify that the scheduler job will report the information

about more than one NFA's down after the configured 'x' time

To verify that the scheduler job will report the information

about more than one NAT down after the configured 'x' time

To verify that whenever we take a new build , then the

updates to Scheduler Job run property value will be retained
to its default value 15 mins

To verify that the scheduler job will report the information

about more than one NFA's down after the configured 'x' time
 Test Steps
General Positive Cases
Verify the NetKnow.Properties file and check for the Schedule Job Run
property to see if user can edit it and provide a value

1) Open Tomcat Manager using the URL "http://{{ws_hostname}}:

{{ws_port}}/manager/html"
2) Click on the Stop button for the service "NetKnow Provision service" and
make sure user will get the confirmation message as "" once the service is
brought down
3) Verify the logs( /var/local/asp.log ) after 15 mins abd check if scheduler
reported any error/status message regarding the NetKnow Provisioning.

1) Open Tomcat Manager using the URL "http://{{ws_hostname}}:

{{ws_port}}/manager/html"
2) Click on the Stop button for the service "NetKnow Order service" and make
sure user will get the confirmation message as "" once the service is brought
down
3) Verify the logs( /var/local/asp.log ) after 15 mins abd check if scheduler
reported any error/status message regarding the NetKnow Order

1) Open Tomcat Manager using the URL "http://{{ws_hostname}}:

{{ws_port}}/manager/html"
2) Click on the Stop button for the service "NetKnow Core service" and make
sure user will get the confirmation message as "" once the service is brought
down
3) Verify the logs( /var/local/asp.log ) after 15 mins abd check if scheduler
reported any error/status message regarding the NetKnow Core

1) Bring Down the ITPAM by Configuring the invalid URL in

NetKnow.Properties file
2) Verify the logs( /var/local/asp.log ) after 15 mins and check if scheduler
reported any error/status message regarding the ITPAM

1) Bring Down the Kore Database by Configuring the invalid URL in

NetKnow.Properties file
2) Verify the logs( /var/local/asp.log ) after 15 mins and check if scheduler
reported any error/status message regarding the Kore Database

1) Bring Down the Kore Transaction by Configuring the invalid URL in

NetKnow.Properties file
2) Verify the logs( /var/local/asp.log ) after 15 mins and check if scheduler
reported any error/status message regarding the Kore Transaction
1) Bring Down the CAPC by Configuring the invalid URL in NetKnow.Properties
file
2) Verify the logs( /var/local/asp.log ) after 15 mins and check if scheduler
reported any error/status message regarding the CAPC

1) Bring Down the NFA by Configuring the invalid URL in NetKnow.Properties

file
2) Verify the logs( /var/local/asp.log ) after 15 mins and check if scheduler
reported any error/status message regarding the NFA

1) Bring Down the NAT by Configuring the invalid URL in NetKnow.Properties

file
2) Verify the logs( /var/local/asp.log ) after 15 mins and check if scheduler
reported any error/status message regarding the NAT

Miscellaneous
1) Open Tomcat Manager using the URL "http://{{ws_hostname}}:
{{ws_port}}/manager/html"
2) Click on the Stop button for the service "Scheduler service" and make sure
user will get the confirmation message as "" once the service is brought down
3) Also click on the stop button for the service "NetKnow Provision" and make
sure that the service is down.
4) Verify the logs( /var/local/asp.log ) after 5 mins abd check if scheduler
reported any error/status message regarding the NetKnow Order

1) Open Tomcat Manager using the URL "http://{{ws_hostname}}:

{{ws_port}}/manager/html"
2) Click on the Stop button for the service "Provision service" and make sure
user will get the confirmation message as "" once the service is brought down
3) Also click on the stop button for the service "NetKnow Core" and make
sure that the service is down.
4) Verify the logs( /var/local/asp.log ) after 5 mins abd check if scheduler
reported any error/status message regarding the NetKnow Order

1) Open Tomcat Manager using the URL "http://{{ws_hostname}}:

{{ws_port}}/manager/html"
2) Click on the Stop button for the service "Provision service" and make sure
user will get the confirmation message as "" once the service is brought down
3) Verify the logs( /var/local/asp.log ) after 5 mins and check if scheduler
reported any error/status message regarding the NetKnow Provision service
1) Bring down the CAPC01 and CAPC02 by configuring the invalid URL for
both the CAPC's.
2) Verify the logs( /var/local/asp.log ) after 5 mins and check if scheduler
reported any error/status message regarding the CAPC01, CAPC02

1) Bring down the NFA01 and NFA02 by configuring the invalid URL for both
the NFA's.
2) Verify the logs( /var/local/asp.log ) after 5 mins and check if scheduler
reported any error/status message regarding the NFA01, NFA02

1) Bring down the NAT01 and NAT02 by configuring the invalid URL for both
the NAT's.
2) Verify the logs( /var/local/asp.log ) after 5 mins and check if scheduler
reported any error/status message regarding the NAT01 , NAT02

1) Modify the Netknow properties file so that chage the property value of
scheduler job from 10 mins to 12 mins. Build
2)Deploy the Latest build into the QA environment.
3) Once build deploy is completed then check the netKnow.Properties file for
the property value of "Scheduler Job Run"

1) Bring down all the services (Provisioning, Order, Kore Databse,Netknow

core, ITPAM,CAPC,NFA,NAT)
2) Verify the Logs after 10 mins and check if scheduler reported any error
messges for the services which are down.
 Expected result

1) User should be allowed to edit the Net Know Properties

file
2) A Property for Schedule Job run should exist in the file so
as user can edit the property value

1) Scheduler should report the error message to the logs(

/var/local/asp.log ) with the below error message after 15
mins when the provision service is down.
"ASP-0190 netknow-provisioning.war file is down
KoreAuditProcess"

1) Scheduler should report the error message to the logs(

/var/local/asp.log ) with the below error message after 15
mins when the Order service is down.
"ASP-0191 netknow-order-services.war file is down
KoreAuditProcess"

1) Scheduler should report the error message to the logs(

/var/local/asp.log ) with the below error message after 15
mins when the Core service is down.
" ASP-0192 netknow-core.war file is down
KoreAuditProcess"

1) Scheduler should report the error message to the logs(

/var/local/asp.log ) with the below error message after 15
mins when the ITPAM is down.
" ASP-0193 ITPAM is not working KoreAuditProcess"

1) Scheduler should report the error message to the logs(

/var/local/asp.log ) with the below error message after 15
mins when the Kore Database is down.
" ASP-0194 Kore Database is not responding
KoreAuditProcess"

1) Scheduler should report the error message to the logs(

/var/local/asp.log ) with the below error message after 15
mins when the Kore Transaction is down.
" ASP-0195 Kore Transaction failed - Network
Connectivity Problems KoreAuditProcess"
1) Scheduler should report the error message to the logs(
/var/local/asp.log ) with the below error message after 15
mins when the CAPC is down.
" ASP-0196 CA PC is Down, <resource name>
KoreAuditProcess"

1) Scheduler should report the error message to the logs(

/var/local/asp.log ) with the below error message after 15
mins when the NFA is down.
" ASP-0197 NFA is Down, <resource name>
KoreAuditProcess"

1) Scheduler should report the error message to the logs(

/var/local/asp.log ) with the below error message after 15
mins when the NAT is down.
" ASP-0198 NAT is Down, <resource name>
KoreAuditProcess"

1) As the scheduler service is down, the schedule job run will

not report the status of any service that is down
2) Scheduler Job will not report the error message for
provision service with the error message "ASP-0190
netknow-provisioning.war file is down KoreAuditProcess" as
the scheduler service itself is down

1) After the configured 'x' time, the scheduler should report

the status of both the services "NetKnow Provision" and
"NetKnow Core" services as below

When the Provision Service is down.

"ASP-0190 netknow-provisioning.war file is down
KoreAuditProcess"

When the Netknow Core service is down...

"ASP-0192 netknow-core.war file is down KoreAuditProcess"

1) Scheduler should report the error message to the logs(

/var/local/asp.log ) with the below error message after 15
mins when the provision service is down.
"ASP-0190 netknow-provisioning.war file is down
KoreAuditProcess"
1) Scheduler should report the error message to the logs(
/var/local/asp.log ) with the below error message after 15
mins when the both CAPC01, CAPC02 services are down.
"ASP-0196 storm-ws01.ca.com CA PC is Down, CAPC01
KoreAuditProcess"
"ASP-0196 storm-ws01.ca.com CA PC is Down, CAPC03
KoreAuditProcess"

1) Scheduler should report the error message to the logs(

/var/local/asp.log ) with the below error message after 15
mins when the both NFA01, NFA02 services are down.
"ASP-0197 NFA is Down, NFA01KoreAuditProcess"
"ASP-0197 NFA is Down, NFA02KoreAuditProcess"

1) Scheduler should report the error message to the logs(

/var/local/asp.log ) with the below error message after 15
mins when the both NAT01, NAT02 services are down.
"ASP-0198 NAT is Down, NAT01KoreAuditProcess"
"ASP-0197 NFA is Down, NAT02KoreAuditProcess"

The scheduler Job run Propertry in the NetKnow.Properties

file would have got updated to 15 mins as it is the default
value

1) When all the services are down then scheduler should

report the following error messages to the log.
ASP-0190 netknow-provisioning.war file is down
KoreAuditProcess
ASP-0191 netknow-order-services.war file is down
KoreAuditProcess
ASP-0192 netknow-core.war file is down KoreAuditProcess
ASP-0193 ITPAM is not working KoreAuditProcess
ASP-0194 Kore Database is not responding KoreAuditProcess
ASP-0195 Kore Transaction failed - Network Connectivity
Problems KoreAuditProcess
ASP-0196 CA PC is Down, <resource name>
KoreAuditProcess
ASP-0197 NFA is Down, <resource name> KoreAuditProcess
ASP-0198 NAT is Down, <resource name> KoreAuditProcess
 Actual Result Status

PASS

PASS - Mon Dec 29 09:40:23 GMT 2015 ASP-

0190 storm-ws01.ca.com netknow-
provisioning.war file is down KoreAuditProcess

PASS - storm-ws01.ca.com netknow-order-

services.war file is down KoreAuditProcess

PASS - storm-ws01.ca.com netknow-core.war file

is down KoreAuditProcess

PASS -