One can now declare todo tests that are not yet implemented

Author: pgrange

bash_unit

@@ -16,7 +16,7 @@
 #
 #  https://github.com/pgrange/bash_unit
 
-VERSION=v1.3.1
+VERSION=v1.4.0
 
 ESCAPE=$(printf "\033")
 NOCOLOR="${ESCAPE}[0m"

docs/man/man1/bash_unit.1

@@ -2,12 +2,12 @@
 .\"     Title: bash_unit
 .\"    Author: [see the "AUTHORS" section]
 .\" Generator: Asciidoctor 1.5.5
-.\"      Date: 2017-06-27
+.\"      Date: 2017-07-03
 .\"    Manual: \ \&
 .\"    Source: \ \&
 .\"  Language: English
 .\"
-.TH "BASH_UNIT" "1" "2017-06-27" "\ \&" "\ \&"
+.TH "BASH_UNIT" "1" "2017-07-03" "\ \&" "\ \&"
 .ie \n(.g .ds Aq \(aq
 .el       .ds Aq '
 .ss \n[.ss] 0
@@ -212,6 +212,9 @@ You may write a \fBteardown\fP function that will be exectuted after each test i
 .sp
 If you need to set someting up only once for all tests, simply write your code outside any test function, this is a bash script.
 .sp
+If you want to keep an eye on a test not yet implemented, prefix the name of the function by \fBtodo\fP instead of test.
+Test to do are not executed and do not impact the global status of your test suite but are displayed in \fBbash_unit\fP output.
+.sp
 \fBbash_unit\fP changes the current working directory to the one of the running test file. If you need to access files from your test code, for instance the script under test, use path relative to the test file.
 .sp
 You may need to change the behavior of some commands to create conditions for your code under test to behave as expected. The \fBfake\fP function may help you to do that, see bellow.