CAA: Unit Test

测试(Test)是软件工程中很重要的一环.CAA提供了UnitTest的可能性(mkODT).可惜我没能找到具体的例子.由于CAA的工作对象是CATPart,CATProduct等Binary文件,给结果比较带来了困难.在"Testing Your Frameworks"一文中(见CAADoc/Doc/online/CAARqcTechArticles/CAARqcOverview.htm),解释OutputRef文件夹的时候,有下面一段话:
  
if you want to test a program which automate some modifications on a CATIA model, you can first perform these modifications "by hand" and save the result in a file you store in the OutputRef directory, then make a comparison (in the shell) between this model and the one produced by the test program in the Output/$OS directory.
  
问题是例如两个CATPart文件如何diff?有这样的diff程序吗?
要是有哪位能给出个.tst的FrameWork源程序,就最理想了.

这个mkODT不是太好用，r12以前升个版本就能让旧的不工作
r16以后要支持64bit,所以所有的测试都要做3遍， 32bit, wow和pure64bit，所以最近自动测试功能很注目了。我们到前个版本大约7万step,光性能测试就有9万项。乘3了话cost太大
  
期望DS能在r16的GA提供实用的工具。省得自己开发了

The CAA Document description is correct. You should not compare the two part document, but compare the content of the two part document.

For instance, On R15 you created a solid object in the part1 and save it to the OutputRef, during every ODT test, you run your test case and generate a new part with another solid object, then you compare these two solid from two part documents, such as there volume,  COG and etc.

It is good way to catch the regression during the development