Testing

Current Status

Item	Status

Item	Status
Testing Blockers	No blocker
High visibility bugs	No highlighted bug
Other issues for testing that should be seen at a summary level	nONE

#	Test Case	Status

#	Test Case	Status
1	DFC consumes 1node/1file event, collects from XNF, then successfully publish it	Not yet tested
2	Interface towards Message-Router -Negative tests	Not yet tested
3	Interface towards xNF -Negative tests	Not yet tested
4	Interface towards Data-Router -Negative tests	Not yet tested
5	XNF temporary disconnection	Not yet tested
6	DR temporary disconnection	Not yet tested
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	Not yet tested
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.	Not yet tested
9	Ensure the connection to xNF is closed. Expected outcome: Connection to xNF is closed.	Not yet tested

	Test environment requirements for above test cases: Docker-compose for XNF simulator MR-sim and DR-sim requirements are fulfilled (virtualenv, npm, or docker-container) The environment can be found in the Integration repo ./test/mocks/

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.