diff --git a/tests/pkg_fatfs_vfs/Makefile b/tests/pkg_fatfs_vfs/Makefile
index e420b54668..3fb1aaffa1 100644
--- a/tests/pkg_fatfs_vfs/Makefile
+++ b/tests/pkg_fatfs_vfs/Makefile
@@ -45,10 +45,6 @@ BOARD_WHITELIST := airfy-beacon arduino-due arduino-duemilanove \
 
 TEST_DEPS += image
 
-# The test requires some manual setup to work
-# So it cannot currently be run
-TEST_ON_CI_BLACKLIST += all
-
 include $(RIOTBASE)/Makefile.include
 
 image:
diff --git a/tests/pkg_fatfs_vfs/README.md b/tests/pkg_fatfs_vfs/README.md
index 9b6a94cf0f..e71a36f89f 100644
--- a/tests/pkg_fatfs_vfs/README.md
+++ b/tests/pkg_fatfs_vfs/README.md
@@ -21,6 +21,8 @@ FAT) That implies it doesn't show any modifications in RIOT that you perform on
 your OS and the other way round. So always remember to mount/unmount correctly
 or your FS will probably get damaged.
 
+    make flash test-with-config
+
 # Real Hardware
 
 Currently the test defaults to sdcard_spi on real hardware. But generally any
@@ -30,3 +32,5 @@ storage device (e.g. your SD-card). To copy the image onto the card you can use
 something like `make image && dd if=bin/riot_fatfs_disk.img
 of=/dev/<your_sdcard>`. After that you can connect the card to your RIOT device
 and check the test output via terminal.
+
+    make flash test-with-config
diff --git a/tests/pkg_fatfs_vfs/tests/01-run.py b/tests/pkg_fatfs_vfs/tests-with-config/01-run.py
similarity index 100%
rename from tests/pkg_fatfs_vfs/tests/01-run.py
rename to tests/pkg_fatfs_vfs/tests-with-config/01-run.py