The final command is: catkin build –verbose –catkin-make-args run_tests | sed -n '/[==========]/,/[==========]/p'..I’m leaving to the reader as a practice to how to multiplex the output of above command to a file and to stdout..One final remark is on the necessity of roscore..If you are dealing with ROS nodes, then you have to have a working instance of roscore before testing process starts.ReleaseFinally, I would like to explain how a ROS package can be released..Note that this is not the only way of doing it and basically outputs an install-able offline Debian package..The convention among ROS developers is to use ROS buildfarm to release binary packages, handle continuous integration of them and etc… I haven’t yet undergone such a process, since I’m participated in a proprietary project.Let’s cut it to the chase!.Catkin also provides native support for installing..Before anything, it is a good convention to clean up the workspace and then give a new configuration to it that we are going to have an installation:catkin clean –yes && catkin config –install –merge-installI’d like to have all the packages in workspace to be merged in install folder..Nevertheless, if you want their install-able targets to be located in their distinct folders, you can also specify –isolate-install flag instead of –merge-install..In this stage, a small application — checkinstall — is required..If you don’t have it in your system, simply run sudo apt-get install checkinstall..It will install a proper version of it.. More details