To run tests, make sure you have TAP::Harness and Test::More installed, and run
prove -Imodules -r
from the kdesrc-build base directory. The -I flag adds kdesrc-build's own internal modules to the search path by default.
This will run all tests under t/, including any (nested) subdirectories.
If you want to run specific tests then do
prove -Imodules t/*.t
Replace the last parameter with the tests you want.

This is vim support for kdesrc-build. To use, place ftdetect/kdesrc-buildrc.vim in your $VIMRUNTIME/ftdetect folder (create the folder if necessary, $VIMRUNTIME is normally ~/.vim). This detects kdesrc-buildrc files.
Additionally place syntax/kdesrc-buildrc.vim in the $VIMRUNTIME/syntax folder (again, create if necessary). This allows Vim to properly highlight your kdesrc-buildrc when it's detected.
Use ":set ft" to see what filetype is detected if it doesn't work.
The highlighting is quite simplistic, many improvements could easily be made for those with interest and some free time....
NOTE: Kate and kwrite support is included in the "kdesrc-buildrc.xml" file that has been included and updated with kdesrc-build for years (and is now part of the KTextEditor framework for KF5). Improvements to that are encouraged as well. :)
- Michael Pyne, mpyne@kde.org, 2014 Aug 08