| # | Test Case | Status |
|---|
| 1 | xNF: Ensure fileReady event is received from xNF at DCAE VES collector. | |
| 2 | DCAE VES Collector: Ensure fileReady event is processed and forwarded to correct topic on DCAE Message Router. | |
3 | DCAE File Collector: Ensure fileReady event is received from DCAE Message Router. | |
| DCAE File Collector: Ensure event is processed and any invalid file entries (i.e. missing or corrupt data) are logged. | |
| 5 | DCAE File Collector: After succesful event parsing, confirm connection to file location is initiated for file retrieval. E.g. connection to xNF file location contained in the event. | |
| 6 | DCAE File Collector: Confirm that if a successful connection can not be made to the location, an error log is raised. E.g. authentication failed, destination unreachable, etc. | |
| 7 | DCAE File Collector: Ensure that for each new entry in the fileReady event the file is retrieved.
| |
| 8 | DCAE File Collector: Ensure any files which are not available are logged. E.g. file no longer on the xNF, logged as non-existant file. | |
| 9 | DCAE File Collector: Confirm that in the event a file fails to transfer successfully, retry is initiated. | |
| 10 | DCAE File Collector: Confirm that in the event the maximum number of retries is exceeded, an error is logged. E.g. file not able to be retrieved. | |
| 11 | DCAE File Collector: Ensure the connection to xNF is closed. | |
| 12 | DCAE File Collector: Ensure the data file(s) retrieved for that processed fileReady event are published to correct feed on DMaaP Data Router. | |
| 13 | DMaaP DR: Confirm that DR client is able to subscribe and receive data file on expected feed. | |
| 14 | DCAE File Collector: Robustness testing. uService failures. uService behaviour tbd, test case to be defined. | |
| 15 | DCAE File Collector: Robustness testing, missed 'fileReady' event handling. uServcie behaviour tbd, test case to be defined. | |
|
|
|
| Test environment requirements for above test cases: - xNF (or emulator) with VES support for 'fileReady' event.
- E.g. xNF able to produce data files and send VES fileReady events,
- E.g. xNF emulator able to produce 'fileReady' notification
event with required content. Ability to modify the contents to send new/modified VES - events including updated events, or a series or predefined VES events at periodic intervals.
- xNF ftpes server.
- sample data files for collection. E.g. 3gpp PM files.
- ONAP platform reqs:
- DMaaP R3, DR running and configured for Bulk PM support
- DCAE R3, MR with support for VES 6.x spec
- DCAE R3, Data File Collector installed and configured
|
|
