Re: Is Aunit helpful?

["Yannick Duchêne (Hibou57)" <yannick_duchene@yahoo.fr>]

Le Thu, 05 Aug 2010 22:39:00 +0200, Ada novice <posts@gmx.us> a écrit:
> gnatmake -Pcalc
> ./harness -v

It seems there is another GNAT 2010 trick here. In project files (*.gpr  
files), this may be required to turn all "-gnatwa.Xe" into "-gnatwa.X".  
"-gnatwa.Xe" tells GPRBuild to treat warnings as error, and there are  
warnings like
“math-test.adb:13:07: warning: call to obsolescent procedure "Assert"  
declared at aunit-assertions.ads:113”
which occurs and would otherwise makes the compilation failed (as this end  
up to be treated as error).

About AUnit: just seen about what it is, how it is set up and how it  
works. Seems a question is still pending : “how to be sure the test cover  
all relevant case ?”. I do not see a way to be sure testing cover all  
cases. That is the main limitation of this kind of approach. May be this  
is nice for regression tests and tests cases revealed during application's  
life time... however, I don't believe this can be used too much soon in a  
development stage. Pretty sure this is best used just after real use or  
deployment has been started.


-- 
There is even better than a pragma Assert: a SPARK --# check.
--# check C and WhoKnowWhat and YouKnowWho;
--# assert Ada;
--  i.e. forget about previous premises which leads to conclusion
--  and start with new conclusion as premise.