- ... core1
- aips, dish, synthesis
and vlbi packages
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ... complete2
- Tools like ``Purify'' and ``TestCenter''
should be used if they are available.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...trial.3
- (your-workspace)/code/trial - at the same logical level as
aips, dish, vlbi, synthesis and all of the site-specific packages
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...tNewClass.cc4
- If there is more than one
test, exec, output or demo program, name subsequent files,
for example tNewClass1.cc, tNewClass2.cc -
the first program is implicitly number zero.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...aips2-cop@nrao.edu5
- If the class source code
amounts to many thousands of lines of text, explain this to the cop -
it may be possible for the reviewer to examine the code ``in place'',
on your machine, or checked in to the trial directory.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ... code.6
- A handy
way to construct a test program for a new class is to copy the class
header file into a new file - which will become the test program -
and edit the member function declarations into member function calls.
This simple approach guarantees that all of the member functions are
called. The next step would be to intentionally call all of the
member functions in such a way that all the exceptions are thrown:
if you trigger and catch all of the exceptions, then you have gone
a long way towards exercising all of the code. ``Domain'' coverage should
be attempted too: exercise the member functions by calling them with a
range of inputs, paying particular attention to the boundaries of the domain.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...
differences7
- We hope that, in time, the AIPS++ project will
find or develop a ``diff'' tool that is smart enough to compare
numbers, and distinguish between allowable differences (due to
word-length round-off) and unacceptable numerical error.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.