Hi everyone.
At this morning's AI meeting we discussed putting unittest information
and programs/scripts into the slim_source gate.
It is important that there be a structure to this, to prevent sprawl and
unorganization. Implementing such a structure now will help maintain
gate organization in the future. If we don't, the gate will degenerate.
I propose that we put test code and documentation into a subdirectories
with an agreed-upon standard name. Each subdirectory will hang off of
the directory containing the delivered code being tested. I suggest
"unittest". The slim-source gate does not contain any matches on this
name currently, and the name is clear.
As an example, I have some XML processing code under
usr/src/lib/install_utils. I will put my test programs for these
modules in usr/src/lib/install_utils/unittest.
Code and documents going into the unittest subdirectories (and *only*
unittest subdirectories) don't need to be code reviewed.
There is some testing code currently in the gate. A find for "test"
shows stuff for ict, orchestrator , td and ti code. I will file a bug
for this once we agree that this is the way to go.
If you have comments, send them ASAP, as we need to get our unittest
code back to the gate right away. To this end, I suggest that comments
for this timeout COB today.
Thanks,
Jack
