On 26 February 2015 at 09:26, Roberto E. Vargas Caballero <k...@shike2.com> wrote: >> A good example for this is how'd you develop a compiler for some >> language: whenever an input program results in a compiler error/bug >> that is non-conforming to the language standard, fix the bug in the >> compiler implementation and record the specific input program as unit >> test for future uses. During time your unit tests will grow an test >> real world problems and not artificial programs that the developer >> came up with while developing and that haven been rendered invalid >> meanwhile. > > But in this case you are talking about functional test or test cases, > I feel they are different to unit test, isn't it?
Depends. If you imagine the compiler as "unit", then the term "unit" test would be adequate. That's why I prefer to just call it test(s), rather. Different people conglomerate different meanings of such terms... -Anselm
