Testing
Current Status
| Item | Status |
|---|---|
| Testing |
| Blockers |
| ||||||||
| High visibility bugs |
| ||||||||
| Other issues for testing that should be seen at a summary level |
|
Test contacts:
Tamas Bakail tamas.bakai@est.tech
Björn Magnusson bjorn.magnusson@est.tech
DCAE Data File Collector
Test Cases and Status: DCAE Data File Collector
| # | Test Case | Status | ||||
|---|---|---|---|---|---|---|
| 1 | DFC consumes 1node/1file event, collects from XNF, then successfully publish it |
| ||||
| 2 | Interface towards Message-Router -Negative tests |
| ||||
3 | Interface towards xNF -Negative tests |
| ||||
4 | Interface towards Data-Router -Negative tests |
| ||||
| 5 | XNF temporary disconnection |
| ||||
| 6 | DR temporary disconnection |
| ||||
| 7 | Ensure any files which are not available are logged. Expected outcome: any errors such as non-existant file (e.g. file removed before retrieval) are logged |
| ||||
| 8 | Confirm that in the event the maximum number of retries is exceeded, an error is logged. Expected outcome: Error log indicating that the file was not able to retrieved. |
| ||||
| 9 | Ensure the connection to xNF is closed. Expected outcome: Connection to xNF is closed. |
| ||||
Test environment requirements for above test cases:
|
| View file | ||||
|---|---|---|---|---|
|
Message router simulator:
- Provides pre-configured FileReady Event replies based on start arguments. The achieved functionality (test-case) is also controlled by that. Use Unix signals to stop/kill as necessary and restart according to TC. Stdout shows the polling and replies.
Data router simulator:
- Consists of two processes of http server to mimic forwarding properly. Use Unix signals to stop/kill as needed. Stdout shows published files. The number of the collected files can be queried using an HTTP interface for CI purposes.
XNF simulator:
- A set of FTPS, SFTP servers prepared with keys/certificates and files to be downloaded.
- Controlled by a docker-compose configuration
- There are NO VES events originated from this to keep the structure simple. All VES events (FileReady Events) are created by the MR-sim based on the pre-populated files and known ports/IP addresses.