Yes, put it to fith-tools is a good suggestion.
But I want to know how will fith-tool directory existing in our =
project.
The code there in is not used for much time, and overdated.
I will try to clean up the directory.
=20
-Kevin
-----Original Message-----
From: Rusty Lynch [mailto:ru...@li...]=20
Sent: 2003=C4=EA1=D4=C29=C8=D5 6:27
To: Zhuang, Louis; Gao, Kevin;
fau...@li...; Wang, Frank; Wang, =
Stanley
Subject: Re: [Fault-injection-developer] RE: About push e100 test cases =
to
our FITH tree
MessageFrom: Zhuang, Louis=20
> These code segment can demostrate some complex usage for FITH,=20
> Maybe we can create 'e100_test' directory under 'codesegments'=20
> for these test.=20
>
> From: Gao, Kevin=20
>> Now FITH is used to test e100 driver for a period of time,=20
>> and there are some test cases for e100 still on another tracking.
>> Why not I push them into our FITH's tree.
>> Is there any issue? or idea?:)
By creating a new e100_test directory under codesegments I assume
you mean creating a new code segment called e100_test. Any code
that is outside the scope of a code segment should not be put in
that location.
We could use a location to put arbitrary test cases. Maybe in=20
the the fith-tool tree? Maybe fith-tool/fith_test/e100/ for all=20
the e100 test, with a README at fith-tool/fith_test/e100/README=20
that explains how to use the test cases?
--rustyl
|
