1. testsuite - ITC(interactive test case) based which is mean when you modify some of vision code, you need type ITC commands on terminal. ITC hides some resource allocation and logics, it makes hard to debug code.
2. assessment - it's basically testsuite with timer so most of code are duplicated.
-mv_test try convert testsuite ITC to unit test and timer function.
+mv_test try convert testsuite ITC to unit test and timer function.
+Since assessment is optional test, it will be `DISABLED_` [optional gtest](https://github.com/google/googletest/blob/master/docs/advanced.md#temporarily-disabling-tests).
+assessment test could be run with `--gtest_also_run_disabled_tests`
## How test?
First test needs dataset https://github.sec.samsung.net/k-son/mv_test.git
## FAQ
### What about Tizen TCT?
Tizen tct is for public API verification. It's still valid however mv_test is more focus on internal APIs.
-Another point is Tizen tct has huge amount of datset of other packages which is not related with media vision so build takes long, and complicated.
+Another point is Tizen tct has huge amount of dataset of other packages which is not related with media vision so build takes long, and complicated.
### Why gtest?
I tried with libcheck but since Tizen API is C/C++, hard to cover all of C++ modules (interal API is more rely on C++).