Testing Fink
Installation and general tests (experts only)
Installing Fink is not too complicated but might be an overwhelming task. Fink can be a complex system, but hopefully it is highly modular such that you do not need all the parts to test one part in particular. If you want to test it fully though, we recommend using the available Docker images, which contain all you need to start (Apache Spark, Apache Kafka, Apache HBase, plus Fink components). You can find these either in the fink-docker repository, or in the fink-broker repository for kubernetes support.
Running the test suite with Docker
In general, you can follow what is done for the continuous integration. Once the image julienpeloton/fink-ci:latest (DockerHub) is pulled, fire a container and set the PYTHONPATH and PATH to use the tools:
# in your ~/.bash_profile
export FINK_HOME=/path/to/fink-broker
export PYTHONPATH=$FINK_HOME:$PYTHONPATH
export PATH=$FINK_HOME/bin:$PATH
The fink-broker repository contains some alerts from the ZTF experiment required for the test suite in the folder datasim. Make sure the test suite is running fine. Just execute:
You should see plenty of Spark logs (and yet we have shut most of them!), but no failures hopefully! Success is silent, and the coverage is printed on screen at the end.
Tests with Kubernetes
You will find at fink-broker/doc/e2e.md all the steps to deploy Fink on Kubernetes, and test the real-time components (DB operations are not tested here).