* add CUTTER_DEBUG technique in test/run-test.sh to tutorial
  as a debugging technique.
* use real data instead of dummy data (e.g. a, b, c, ...)
  for demo screenshot. (It's more realistic)
* add 'what merit we will get' instead of 'what features we
  will get' to introduction document.
* add 'how to become a test junkie from a test amateur' to document.
* cut_thread_create(): it pushes the current test context. tests written by
  user will not care the current test context.
* priority mode.
* auto-cutter.
* gompertz curve.
* elapsed time assert. (compare with past elapsed time?)
* test history chart.
  * N tests
  * N failures
  * elapsed time
* coordinattion with TestLink.
* failmalloc like memory test.
* update option descriptions in README.
* introduce easy sub process debugging mechanism.
* cut_assert_equal_sockaddr().
* GTK+ UI supports test iterator.
* cut_get_test_name().
* cut_{get,set}_current_test_context() ->
  cut_{get,set}_test_context()
