NOTE:

1) The scope of testing for this user story is for verifying the different NMS_PRODUCT_STATUS of NIMSOFT devices.
2) Currently, the scope of testing is just only upto the ADD orders.
USER STORY DETAILS(US #190849):
Once the device is imported and assigned to the correct Group and PBM has assigned the correct template,
Use the metric API to confirm that the secondary discovery has happened.
If it does not then the device goes into a error state for the NMS Product. This should be an informative error state, so tha
Timeout for 2 hours - Configurable, some devices can take a long time to successfully complete a component discovery

Demonstration: Show that the status is changed if the component discovery fails.

NOTE: for dev and testing, we are not testing PBM with this story, we are testing the ability to see metrics from a device that ha
a sucess.

TestCase ID Pre Condition Test Case Description

TC-001 To verify that user can successfully process add order
for the Nimsoft device

TC-002 To verify that the Nimsoft order will fail after 2 hours
when user process the Nimsoft Order with Community
string as NetKnow

TC-003 To verify that the Nimsoft order will fail after 2 hours
when user process the Nimsoft Order with Community
string as invalid value

TC-004 configure property value as 2 hours for To verify that NMS PRODUCT_STATUS waill remain in
scheduler to run IN_INVENTORY untill scheduler service is not up

TC-005 configure property value as 2 hours for To verify that NMS PRODUCT_STATUS will get failed
scheduler to run when user do not process the SNMP collector details
to Nimsoft for 2 hours with having the Produict Status
to IN_INVENTORY.

TC-006 To verify that the NMS product status will not get
impacted with the scheduler servie when the user
brings up the scheduler service when the product
status is in IN_INVENTORY
TC-007 To verify that Processing of a Nimsoft order for the
same data for which the product status is
IN_INVENTORY will fail at order level

TC-008 To verify that processing of a Nimsoft order for the

existing data which got order status as FAILED will also
fail as the system will not allow duplicate data
processing in the system

TC-009 To verify that the Tomcat restart of the system when

the NMS Product Status is IN_INVENTORY will not
affect the order processing as the system waits for the
scheduler service to pickup for furthur processing of
order

TC-010 To verify that the Tomcat restart of the system will fail
the order when the NMS Product Status is
IN_INVENTORY and not adding the snmp collector
details to NIMSFOT

TC-011 To verify that Restarting the tomcat after when user

manually adds the SNMP collector details to NIMSOFT,
will make the scheduler to pickup the order for
processing and updates the PRODUCT status
accordingly

TC-012 To verify that Restarting the tomcat before when user

manually adds the SNMP collector details to NIMSOFT,
will make the scheduler to pickup the order for
processing and updates the PRODUCT status
accordingly

TC-013 To verify that Restarting the tomcat after when user

manually adds the SNMP collector details to NIMSOFT
for a NIMSOFT Order with community string as
Netknow will fail the order after two hours

TC-014 To verify that Restarting the tomcat before when user

manually adds the SNMP collector details to NIMSOFT
for a NIMSOFT Order with community string as
Netknow will fail the order after two hours
TC-015 To verify that when user process a DELETE order for
the existing Nimsoft order for which the
PRODUCT_STATUS is New will process the delete order
successfully before the order is processed

TC-016 To verify that when user process a DELETE order for

the existing Nimsoft order for which the
PRODUCT_STATUS is IN_INVENTORY, will wait for the
order to get processed first and then gets the delete
order processed later
SOFT devices.

template,

mative error state, so that we know it failed secondary discovery. (create a new NMS Product state)
te a component discovery

trics from a device that has been assigned to a SNMPCOLLECTOR probe. So you can add the IP Address to a SNMPCOLLECTOR probe and te

Test Steps
1) Process a Nimsoft Order with Community String as Public
2) When NMS_PRODUCT_STATUS is IN_INVENTORY, add device manually to Nimsoft
3)Verify and check if the scheduler picks up the record for processing and marks the
NMS_PRODUCT_STATUS as PROVISIONED

1) Process a Nimsoft Order with Community String as Netknow

2) When NMS_PRODUCT_STATUS is IN_INVENTORY, add device manually to Nimsoft
3)Verify and check if the scheduler picks up the record for proceseing and fails after 2 hours

1) Process a Nimsoft Order with Community String as Invalid Value

2) When NMS_PRODUCT_STATUS is IN_INVENTORY, add device manually to Nimsoft
3)Verify and check if the scheduler picks up the record for proceseing and fails after 2 hours

1) Process a Nimsoft order with Scheduler service Down

2) Make sure that the NMS status is IN_INVENTORY
3) Verify after two hours to see if the NMS status gets updated to some other value other than
IN_INVENTORY

1) Process a Nimsoft order

2) Make sure that the NMS status is IN_INVENTORY
3) Do not process the SNMP collector details manually to NIMSFOT
4) Verify the Product_status in DEV_CUSTPROD_COLLECTOR_REF Table after 2 hours

1)Bring Down the scheduler service

2) Process a Nimsoft order
3) Make sure that the NMS status is IN_INVENTORY
4) Bring up the scheduler service
3) process the SNMP collector details manually to NIMSFOT
4) Verify the Product_status in DEV_CUSTPROD_COLLECTOR_REF Table after 2 hours
1) Process a Nimsoft order
2) Make sure that the NMS status is IN_INVENTORY
3) Process a Nimsoft order for the same data .
4) Verify the order response

1) Process a Nimsoft order with Invalid community string

2) make sure that the order will fail after 2 hours with updating the product status as
Metric_collection_fail.
3) Process the same set of order data for Nimsoft correcting the community string.
4) verify the order response

1) Process a Nimsoft order with community string as Public

2) Make sure that the PRODUCT_STATUS is IN_INVENTORY
3) Restart the tomcat
4) Manually add the SNMP Collector details to NIMSOFT.
5) verify the PRODUCT STATUS after two hours

1) Process a Nimsoft order with community string as Public

2) Make sure that the PRODUCT_STATUS is IN_INVENTORY
3) Restart the tomcat
4) Do not add the SNMP Collector details to NIMSOFT.
5) verify the PRODUCT STATUS after two hours

1) Process a Nimsoft order with community string as Public with bringing down the Scheduler
service
2) Make sure that the PRODUCT_STATUS is IN_INVENTORY
3) Manually add the SNMP Collector details to NIMSOFT.
4) Restart the Tomcat of the machine.
5) make sure that the Metrics were collected for the device
6) verify the PRODUCT STATUS after two hours

1) Process a Nimsoft order with community string as Public with bringing down the Scheduler
service
2) Make sure that the PRODUCT_STATUS is IN_INVENTORY
3) Restart the Tomcat of the machine.
4) Manually add the SNMP Collector details to NIMSOFT.
5) make sure that the Metrics were collected for the device
6) verify the PRODUCT STATUS after two hours

1) Process a Nimsoft order with community string as Netknow with bringing down the Scheduler
service
2) Make sure that the PRODUCT_STATUS is IN_INVENTORY
3) Manually add the SNMP Collector details to NIMSOFT.
4) Restart the Tomcat of the machine.
5) verify the PRODUCT STATUS after two hours

1) Process a Nimsoft order with community string as Public with bringing down the Scheduler
service
2) Make sure that the PRODUCT_STATUS is IN_INVENTORY
3) Restart the Tomcat of the machine.
4) Manually add the SNMP Collector details to NIMSOFT.
5) verify the PRODUCT STATUS after two hours
1) Process a NIMSOFT order with community string as public
2) Make sure that the product status is NEW
3) Process one DELETE order for the same data
4) verify the Device Status , Product_status

1) process a NIMSFOT order with community string as public

2) Make sure that the order status as IN_INVENTORY
3) Process the DELETE order for the same data
4) verify the Device status, Product_status
ss to a SNMPCOLLECTOR probe and test these results. Even one metric will be

Expected result Actual Result

Once the scheduler picks up the record successfully after finding
the metrics collected for device is successful then it will set the
NMS_PRODUCT_STATUS to PROVISIONED PASS

The scheduler will mark the NMS_PRODUCT_STATUS as

METRIC_COLLECTION_FAILED for community string as Netknnow
PASS

The scheduler will mark the NMS_PRODUCT_STATUS as

METRIC_COLLECTION_FAILED for community string as Invalid Value
PASS

The NMS status will remain as IN_INVENTORY untill the Scheduler

service is up
PASS

As the SNMP collector details havent got procesed manually into

Nimsoft, the scheduler verifies the device metrics not collected
and updates the PRODUCT_STATUS to metrics_collection_fail PASS

Once the scheduler picks up the record successfully after finding

the metrics collected for device is successful then it will set the
NMS_PRODUCT_STATUS to PROVISIONED
PASS
The order should fail at order level itself as the same data is being
processed by the system
PASS

The order should fail at the order level tself as the system will not
process duplicate data
PASS

When user restarts the tomcat, the system waits for the scheduler
service to pick up the order for processing and checks for metric
collection and updates the PRODUCT STATUS to PROVISIONED if
metrics collected else it updates the PRODUCT STATUS to PASS
metric_collection_fail

When the user restarts the tomcat, the scheduler will not pickup
the order for processing as the user has not manually added the
SNMP collector details to the NIMSOFT
PASS

As the SNMP collector details are manually added to NIMSFOT and

restarted the tomcat, then the scheduler service will pickup the
order for processing and updates the PROCUST_STATUS to
PROVISIONED
PASS

As the tomcat restart happened before manually adding the snmp

collector details to NIMSFOT, then the scheduler service will pickup
the order for processing and updates the PROCUST_STATUS to
PROVISIONED
PASS

As the community string is Netknow, the order will fail after 2

hours

PASS

As the community string is Netknow, the order will fail after 2

hours

PASS
As the status of PRODUCT_STATUS is static , the DELETE order gets
processed successfully with updating the PRODUCT_STATUS as
deleted and updating the device status as deleted
PASS

As the status of PRODUCT_STATUS is NON static, the order will get

processed first and then later the delete order gets processed
successfully with updating the PRODUCT_STATUS to deleted and
Device status to deleted PASS
Status Regression Status
 AGENDA:

Observations to mentor:

Suggestions:

Development activities

Assumptions
 AGENDA:
Objective of meeting
What is the mentor telling
What is the mentor suggesting for good relation of people
what are the future plans for better reaching people

Observations to mentor:
Religious conversions
Media back stabbing efforts
Anti conversion law

Suggestions:
Know the benefits that othr religions are giving when being converted
bring pressure on GOVT and media publicly using awareness to people
highlight and catch occasions and shoot it recording and show it in media of other religious conversional
highlight and catch red handedly of other religious heads doing illegal crimes and other fanatic activities
atleast once in a year rath yatra from TTD/Hindu Dharmic trusts should be done to teach importance of culture and traditio
list the out the media which is more anti to sanathandharma and showing negatively about hindu culture and trap them pu
Main and chief mentors/good suggestion giving people names should not be made public within grp as it will help
prepare atleast some tactical leaders for the party for next term elections. And propose them in some good posts and ma
people from grp are for the country and for the sanathan dhram
Development activities
Adopt atleast one village in a mandal and develop it using sanathan dharmic style.
help poor children providing books, dress, chappals
help widow women and provide them some money so that they can do some handwork for earning money
Help poor children on getting jobs once they complete their education and make them to realise sanathan dharma is for th
Help old age people and make to believe that our grp is there for taking care of them
construct some sathras at the temples and provide free food for people with good quality
Assumptions
what currently common man thinks? Is it about religion..? Is it about his clothes? Is it about his children..?Is it about the
how can we be helpful to women in the society?
how can we be helpful to politics?
how can we be helpful to society .?
currently the status of the country is degrading with the problems and attacks like staining for food, rapes, attack on wome
attack on the sanathan dharma, atack on secularistic principles
Is this for what our great country survived since centuries ..?What is our greatness and why the whole world is praising ou

what are we giving to our children..? Is it freedom or the freedom of free style?
what have we learnt from our parents..?
what are we giving to the future children of our country?Is it just the technology without moral values and ethics..?is it ju
Sno
1
2
3
4
5
6
7
8
9
10

11

12

13

14

15

16
 Test Case
Add Nimsoft Order with Community String as Public
Add Nimsoft order with Community String as NetKnow
Add Nimsoft order with community string as "XYZ123"
Add Nimsoft Order with bringing down the scehduler service
Add nimsoft order with configuration scheduler service for 1 hour to search for metric collcetion
Add nimsoft order with Scheduler service as down and bring up the scheduler service up when the NMS_PRODUCT_STATU
Add Nimsoft order for the same set of data when the first order is still in processing
Add Nimsoft order for the same set of data which has got failed due to invalid community string
Add Nimsoft order with community string as public and restart the tomcat server when the NMS_PRODUCT_STATUS is IN_
Add Nimsoft order with valid Community string and check that the NMS product status will remain as IN_INNVENTORY if u
1)Add Nimsoft Order with scheduler service down
2) When NMS status is IN_INVENTORYAdd the Ip address manually to nimsoft
3) Restart the tomcat
4) Bring up the Scheduler service

1)Add Nimsoft Order with scheduler service down

2) When NMS status is IN_INVENTORY,Restart the tomcat
3) Add the Ip address manually to nimsoft
4) Bring up the Scheduler service

1)Add Nimsoft Order with scheduler service down

2) When NMS status is IN_INVENTORY,Restart the tomcat
3) Bring up the scheduler service
4) Add the Ip address manually to nimsoft

1)Add Nimsoft Order with scheduler service down

2) When NMS status is IN_INVENTORYAdd the Ip address manually to nimsoft
3) Restart the activeMq
4) Bring up the Scheduler service

1)Add Nimsoft Order with scheduler service down

2) When NMS status is IN_INVENTORY,Restart the activeMq
3) Add the Ip address manually to nimsoft
4) Bring up the Scheduler service

1)Add Nimsoft Order with scheduler service down

2) When NMS status is IN_INVENTORY,Restart the activeMq
3) Bring up the scheduler service
4) Add the Ip address manually to nimsoft