Hi, Darren.
Yes, that is correct.
The test specification had been renumbered by the past update.
The test specification can change test number easily
because that is originally MS Word document.
In the other hand,
the test tool can not change filename easily
because we manage the modification record by CVS.
Please ignore the file name and believe only HTML output.
Thanks,
On Fri, 24 Jul 2009 14:29:30 +0000
"Hartman, Darren" <dhartman@icsalabs.com> wrote:
>
> Hello,
>
> In some of the INDEX files in Self_Test_4-0-5\nd.p2 there are
> differences between the test numbers and the names of the .seq
> files being executed, whereas in other INDEX files (for example,
> those in the spec.p2 directory) the test reference always correlates
> to the name of the .seq file.
>
>
> Here is one example (INDEX_ND_p2_host file):
> #--------------------------------------------------------------------#
> # v6LC.2.1.4 Host Prefix List (Hosts Only) #
> #--------------------------------------------------------------------#
> &print:<TT>Test v6LC.2.1.4: Host Prefix List (Hosts Only)</TT>
> ./V6LC_2_1_5_A.seq:./V6LC_2_1_5_A.def:::<TT>Part A: Prefix
> Lifetime has not Expired</TT>:1
> ./V6LC_2_1_5_B.seq:./V6LC_2_1_5_B.def:::<TT>Part B: Prefix
> Lifetime updated by Router Advertisement</TT>:1
>
>
> Even though the .seq file is named V6LC_2_1_5_A.seq, it seems to
> be executing tests as defined by the Core Test Specification for
> Test v6LC.2.1.4. There are several other examples as well.
>
> Is this correct?
>
> Regards,
> Darren
>
>
>
>
--
Yukiyo Akisada <akisada@tahi.org>