Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

#Test CasesStatus
1 Resource Definition


Status
titleNot yet tested

2

 Service Definition
Status
titleNot yet tested


3

Type Modeling Artifacts

Status
titleNot yet tested

4

Resource Declaration

Status
titleNot Yet Tested

5Create A&AI PNF Entry

Status
titleNot yet tested

6Service Instantiation

Status
titleNot yet tested

7Homing OOF Scenario

Status
titleNot yet tested

8Resource RLF

Status
titleNot yet tested

9Check A&AI Entry

Status
titleNot yet tested

10Create A&AI Entry

Status
titleNot yet tested

11Subscribe VES Event

Status
titleNot yet tested

12RLF Thread Terminates

Status
titleNot yet tested

13Authenticates PNF Connection

Status
titleNot yet tested

14PNF Registration VES Events

Status
titleNot yet tested

15Inventory Query

Status
titleNot yet tested

16Update PNF Entry

Status
titleNot yet tested

17PNF Ready

Status
titleNot yet tested

...

#

Test Cases

Status

1Confirm that "osam" topic is created in DMAAP.
NOT YET TESTED
2Confirm that VES Collector receives events from OSAM GW's Ves Agent.
NOT YET TESTED
3

Confirm that Ves Collector publishes the alarm event to DMAAP with "osam/alert"

topic tag.

NOT YET TESTED
4Confirm that Service Flow Manager can consume the "osam/alert" topic.
NOT YET TESTED
5Confirm that TCA receives the topic and stores in the BigData DB
NOT YET TESTED







Test environment requirements for above test cases:

  • OSAM GW must be onboarded and instantiated.
  • OSAM Core must be onboarded and instantiated.
  • SEBA service must be onboarded and instantiated.
  • Somehow(maybe from SDC) "osam" topic must be created on DMAAP.
  • At design time CLAMP must be used for OSAM specific Ves flows.

...