#! perl # Copyright (C) 2006, The Perl Foundation. # $Id: 00-qualify.t 16894 2007-02-04 22:54:29Z jkeenan $ # 00-qualify.t use strict; use warnings; use Test::More tests => 11; use FindBin; use lib ( "$FindBin::Bin/../../../lib", ); use_ok( 'Parrot::Ops2pm::Utils' ); ok(-f "$FindBin::Bin/../../../Makefile", "Makefile located"); ok(-f "$FindBin::Bin/../../../myconfig", "myconfig located"); ok(-f "$FindBin::Bin/../../../lib/Parrot/OpsFile.pm", "lib/Parrot/OpsFile.pm located"); ok(-f "$FindBin::Bin/../../../src/ops/core.ops", "src/ops/core.ops located"); ok(-f "$FindBin::Bin/../../../src/ops/ops.num", "src/ops/ops.num located"); ok(-f "$FindBin::Bin/../../../src/ops/ops.skip", "src/ops/ops.skip located"); ok(! -e "$FindBin::Bin/../../../lib/Parrot/OpLib/core.pm", "lib/Parrot/OpLib/core.pm correctly does not yet exist"); ok(! -e "$FindBin::Bin/../../../include/parrot/oplib/ops.h", "include/parrot/oplib/ops.h correctly does not yet exist"); my $message = <and F. By doing so, they test the functionality of the F utility. That functionality has largely been extracted into the methods of F. Since F is invoked near the beginning of the build process, tests of its functionality can give meaningful results only if they are run in a way that simulates the status of the file system at the point at which F invokes F. The tests in F<00-qualify.t> attempt to confirm that you are at that point. They test for the presence or absence of certain files to form a judgment as to whether F has been run (it should have been) and whether F has been run (it should I have been). The tests make certain assumptions about what files should be present or not -- assumptions which may be invalid if the Parrot build process changes in the future. =head1 AUTHOR James E Keenan =head1 SEE ALSO Parrot::Ops2pm::Utils, F. =cut