@@ -1,31 +0,0 @@
-use 5.006;
-use strict;
-use warnings;
-use Module::Build;
-
-my $builder = Module::Build->new(
- module_name => 'Test::Database',
- license => 'perl',
- dist_author => 'Philippe Bruhat (BooK) <book@cpan.org>',
- dist_version_from => 'lib/Test/Database.pm',
- requires => {
- 'DBI' => 1,
- 'File::HomeDir' => 0.50,
- 'version' => 0,
- 'YAML::Tiny' => 1.27,
- 'File::Spec' => 0,
- 'File::Path' => 0,
- 'perl' => 5.006,
- },
- build_requires => {
- 'Test::More' => 0,
- },
- meta_merge => {
- resources => {
- repository => 'http://github.com/book/Test-Database',
- },
- },
- add_to_cleanup => [ 'Test-Database-*' ],
-);
-
-$builder->create_build_script();
@@ -1,5 +1,21 @@
Revision history for Test-Database
+1.112 Sat Mar 22 2014
+ [IMPROVEMENTS]
+ - use File::HomeDir's my_home() instead of my_data() (RT #93678)
+ - require YAML::Tiny 1.62 (RT #92916)
+
+1.111 Sun Mar 9 2014
+ [IMPROVEMENTS]
+ - the default value for username() and password() is now undef
+ (RT #93128, thanks to TIMB)
+ [TESTS]
+ - pod tests are now "release" tests, thanks to dzil (RT #85198)
+ [DOCUMENTATION]
+ - declare character encoding for files not in us-ascii (RT #92660)
+ - point to Test::Database::Tutorial in the DESCRIPTION (RT #78337)
+ - improve linkability by having each method at the =head2 level
+
1.11 Tue May 4 01:03:10 CEST 2010
[IMPROVEMENTS]
- new version_string() method ensures version constraints on
@@ -0,0 +1,379 @@
+This software is copyright (c) 2014 by Philippe Bruhat (BooK).
+
+This is free software; you can redistribute it and/or modify it under
+the same terms as the Perl 5 programming language system itself.
+
+Terms of the Perl programming language system itself
+
+a) the GNU General Public License as published by the Free
+ Software Foundation; either version 1, or (at your option) any
+ later version, or
+b) the "Artistic License"
+
+--- The GNU General Public License, Version 1, February 1989 ---
+
+This software is Copyright (c) 2014 by Philippe Bruhat (BooK).
+
+This is free software, licensed under:
+
+ The GNU General Public License, Version 1, February 1989
+
+ GNU GENERAL PUBLIC LICENSE
+ Version 1, February 1989
+
+ Copyright (C) 1989 Free Software Foundation, Inc.
+ 51 Franklin St, Suite 500, Boston, MA 02110-1335 USA
+
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The license agreements of most software companies try to keep users
+at the mercy of those companies. By contrast, our General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. The
+General Public License applies to the Free Software Foundation's
+software and to any other program whose authors commit to using it.
+You can use it for your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Specifically, the General Public License is designed to make
+sure that you have the freedom to give away or sell copies of free
+software, that you receive source code or can get it if you want it,
+that you can change the software or use pieces of it in new free
+programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of a such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must tell them their rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License Agreement applies to any program or other work which
+contains a notice placed by the copyright holder saying it may be
+distributed under the terms of this General Public License. The
+"Program", below, refers to any such program or work, and a "work based
+on the Program" means either the Program or any work containing the
+Program or a portion of it, either verbatim or with modifications. Each
+licensee is addressed as "you".
+
+ 1. You may copy and distribute verbatim copies of the Program's source
+code as you receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice and
+disclaimer of warranty; keep intact all the notices that refer to this
+General Public License and to the absence of any warranty; and give any
+other recipients of the Program a copy of this General Public License
+along with the Program. You may charge a fee for the physical act of
+transferring a copy.
+
+ 2. You may modify your copy or copies of the Program or any portion of
+it, and copy and distribute such modifications under the terms of Paragraph
+1 above, provided that you also do the following:
+
+ a) cause the modified files to carry prominent notices stating that
+ you changed the files and the date of any change; and
+
+ b) cause the whole of any work that you distribute or publish, that
+ in whole or in part contains the Program or any part thereof, either
+ with or without modifications, to be licensed at no charge to all
+ third parties under the terms of this General Public License (except
+ that you may choose to grant warranty protection to some or all
+ third parties, at your option).
+
+ c) If the modified program normally reads commands interactively when
+ run, you must cause it, when started running for such interactive use
+ in the simplest and most usual way, to print or display an
+ announcement including an appropriate copyright notice and a notice
+ that there is no warranty (or else, saying that you provide a
+ warranty) and that users may redistribute the program under these
+ conditions, and telling the user how to view a copy of this General
+ Public License.
+
+ d) You may charge a fee for the physical act of transferring a
+ copy, and you may at your option offer warranty protection in
+ exchange for a fee.
+
+Mere aggregation of another independent work with the Program (or its
+derivative) on a volume of a storage or distribution medium does not bring
+the other work under the scope of these terms.
+
+ 3. You may copy and distribute the Program (or a portion or derivative of
+it, under Paragraph 2) in object code or executable form under the terms of
+Paragraphs 1 and 2 above provided that you also do one of the following:
+
+ a) accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of
+ Paragraphs 1 and 2 above; or,
+
+ b) accompany it with a written offer, valid for at least three
+ years, to give any third party free (except for a nominal charge
+ for the cost of distribution) a complete machine-readable copy of the
+ corresponding source code, to be distributed under the terms of
+ Paragraphs 1 and 2 above; or,
+
+ c) accompany it with the information you received as to where the
+ corresponding source code may be obtained. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form alone.)
+
+Source code for a work means the preferred form of the work for making
+modifications to it. For an executable file, complete source code means
+all the source code for all modules it contains; but, as a special
+exception, it need not include source code for modules which are standard
+libraries that accompany the operating system on which the executable
+file runs, or for standard header files or definitions files that
+accompany that operating system.
+
+ 4. You may not copy, modify, sublicense, distribute or transfer the
+Program except as expressly provided under this General Public License.
+Any attempt otherwise to copy, modify, sublicense, distribute or transfer
+the Program is void, and will automatically terminate your rights to use
+the Program under this License. However, parties who have received
+copies, or rights to use copies, from you under this General Public
+License will not have their licenses terminated so long as such parties
+remain in full compliance.
+
+ 5. By copying, distributing or modifying the Program (or any work based
+on the Program) you indicate your acceptance of this license to do so,
+and all its terms and conditions.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the original
+licensor to copy, distribute or modify the Program subject to these
+terms and conditions. You may not impose any further restrictions on the
+recipients' exercise of the rights granted herein.
+
+ 7. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of the license which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+the license, you may choose any version ever published by the Free Software
+Foundation.
+
+ 8. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 9. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+ 10. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ Appendix: How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to humanity, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these
+terms.
+
+ To do so, attach the following notices to the program. It is safest to
+attach them to the start of each source file to most effectively convey
+the exclusion of warranty; and each file should have at least the
+"copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the program's name and a brief idea of what it does.>
+ Copyright (C) 19yy <name of author>
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 1, or (at your option)
+ any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston MA 02110-1301 USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) 19xx name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the
+appropriate parts of the General Public License. Of course, the
+commands you use may be called something other than `show w' and `show
+c'; they could even be mouse-clicks or menu items--whatever suits your
+program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the
+ program `Gnomovision' (a program to direct compilers to make passes
+ at assemblers) written by James Hacker.
+
+ <signature of Ty Coon>, 1 April 1989
+ Ty Coon, President of Vice
+
+That's all there is to it!
+
+
+--- The Artistic License 1.0 ---
+
+This software is Copyright (c) 2014 by Philippe Bruhat (BooK).
+
+This is free software, licensed under:
+
+ The Artistic License 1.0
+
+The Artistic License
+
+Preamble
+
+The intent of this document is to state the conditions under which a Package
+may be copied, such that the Copyright Holder maintains some semblance of
+artistic control over the development of the package, while giving the users of
+the package the right to use and distribute the Package in a more-or-less
+customary fashion, plus the right to make reasonable modifications.
+
+Definitions:
+
+ - "Package" refers to the collection of files distributed by the Copyright
+ Holder, and derivatives of that collection of files created through
+ textual modification.
+ - "Standard Version" refers to such a Package if it has not been modified,
+ or has been modified in accordance with the wishes of the Copyright
+ Holder.
+ - "Copyright Holder" is whoever is named in the copyright or copyrights for
+ the package.
+ - "You" is you, if you're thinking about copying or distributing this Package.
+ - "Reasonable copying fee" is whatever you can justify on the basis of media
+ cost, duplication charges, time of people involved, and so on. (You will
+ not be required to justify it to the Copyright Holder, but only to the
+ computing community at large as a market that must bear the fee.)
+ - "Freely Available" means that no fee is charged for the item itself, though
+ there may be fees involved in handling the item. It also means that
+ recipients of the item may redistribute it under the same conditions they
+ received it.
+
+1. You may make and give away verbatim copies of the source form of the
+Standard Version of this Package without restriction, provided that you
+duplicate all of the original copyright notices and associated disclaimers.
+
+2. You may apply bug fixes, portability fixes and other modifications derived
+from the Public Domain or from the Copyright Holder. A Package modified in such
+a way shall still be considered the Standard Version.
+
+3. You may otherwise modify your copy of this Package in any way, provided that
+you insert a prominent notice in each changed file stating how and when you
+changed that file, and provided that you do at least ONE of the following:
+
+ a) place your modifications in the Public Domain or otherwise make them
+ Freely Available, such as by posting said modifications to Usenet or an
+ equivalent medium, or placing the modifications on a major archive site
+ such as ftp.uu.net, or by allowing the Copyright Holder to include your
+ modifications in the Standard Version of the Package.
+
+ b) use the modified Package only within your corporation or organization.
+
+ c) rename any non-standard executables so the names do not conflict with
+ standard executables, which must also be provided, and provide a separate
+ manual page for each non-standard executable that clearly documents how it
+ differs from the Standard Version.
+
+ d) make other distribution arrangements with the Copyright Holder.
+
+4. You may distribute the programs of this Package in object code or executable
+form, provided that you do at least ONE of the following:
+
+ a) distribute a Standard Version of the executables and library files,
+ together with instructions (in the manual page or equivalent) on where to
+ get the Standard Version.
+
+ b) accompany the distribution with the machine-readable source of the Package
+ with your modifications.
+
+ c) accompany any non-standard executables with their corresponding Standard
+ Version executables, giving the non-standard executables non-standard
+ names, and clearly documenting the differences in manual pages (or
+ equivalent), together with instructions on where to get the Standard
+ Version.
+
+ d) make other distribution arrangements with the Copyright Holder.
+
+5. You may charge a reasonable copying fee for any distribution of this
+Package. You may charge any fee you choose for support of this Package. You
+may not charge a fee for this Package itself. However, you may distribute this
+Package in aggregate with other (possibly commercial) programs as part of a
+larger (possibly commercial) software distribution provided that you do not
+advertise this Package as a product of your own.
+
+6. The scripts and library files supplied as input to or produced as output
+from the programs of this Package do not automatically fall under the copyright
+of this Package, but belong to whomever generated them, and may be sold
+commercially, and may be aggregated with this Package.
+
+7. C or perl subroutines supplied by you and linked into this Package shall not
+be considered part of this Package.
+
+8. The name of the Copyright Holder may not be used to endorse or promote
+products derived from this software without specific prior written permission.
+
+9. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED
+WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
+MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
+
+The End
+
@@ -1,22 +1,25 @@
-Build.PL
+# This file was automatically generated by Dist::Zilla::Plugin::Manifest v5.012.
Changes
+LICENSE
+MANIFEST
+META.yml
+Makefile.PL
+README
+dist.ini
eg/MyDriver.pm
lib/Test/Database.pm
lib/Test/Database/Driver.pm
lib/Test/Database/Driver/CSV.pm
lib/Test/Database/Driver/DBM.pm
-lib/Test/Database/Driver/mysql.pm
lib/Test/Database/Driver/Pg.pm
lib/Test/Database/Driver/SQLite.pm
lib/Test/Database/Driver/SQLite2.pm
+lib/Test/Database/Driver/mysql.pm
lib/Test/Database/Handle.pm
lib/Test/Database/Tutorial.pod
lib/Test/Database/Util.pm
-Makefile.PL
-MANIFEST This list of files
-META.yml
-README
t/00-load.t
+t/000-report-versions-tiny.t
t/08-handle.t
t/09-handle-dsn.t
t/10-drivers.t
@@ -34,3 +37,6 @@ t/database.good
t/database.rc
t/pod-coverage.t
t/pod.t
+t/release-distmeta.t
+t/release-pod-coverage.t
+t/release-pod-syntax.t
@@ -1,46 +1,36 @@
---
-name: Test-Database
-version: 1.11
+abstract: 'Database handles ready for testing'
author:
- 'Philippe Bruhat (BooK) <book@cpan.org>'
-abstract: Database handles ready for testing
-license: perl
-resources:
- license: http://dev.perl.org/licenses/
- repository: http://github.com/book/Test-Database
-requires:
- DBI: 1
- File::HomeDir: 0.5
- File::Path: 0
- File::Spec: 0
- YAML::Tiny: 1.27
- perl: 5.006
- version: 0
build_requires:
- Test::More: 0
-provides:
- Test::Database:
- file: lib/Test/Database.pm
- version: 1.11
- Test::Database::Driver:
- file: lib/Test/Database/Driver.pm
- Test::Database::Driver::CSV:
- file: lib/Test/Database/Driver/CSV.pm
- Test::Database::Driver::DBM:
- file: lib/Test/Database/Driver/DBM.pm
- Test::Database::Driver::Pg:
- file: lib/Test/Database/Driver/Pg.pm
- Test::Database::Driver::SQLite:
- file: lib/Test/Database/Driver/SQLite.pm
- Test::Database::Driver::SQLite2:
- file: lib/Test/Database/Driver/SQLite2.pm
- Test::Database::Driver::mysql:
- file: lib/Test/Database/Driver/mysql.pm
- Test::Database::Handle:
- file: lib/Test/Database/Handle.pm
- Test::Database::Util:
- file: lib/Test/Database/Util.pm
-generated_by: Module::Build version 0.33
+ File::Find: '0'
+ File::Temp: '0'
+ List::Util: '0'
+ SQL::Statement: '0'
+ Test::More: '0.88'
+configure_requires:
+ ExtUtils::MakeMaker: '6.30'
+dynamic_config: 0
+generated_by: 'Dist::Zilla version 5.012, CPAN::Meta::Converter version 2.133380'
+license: perl
meta-spec:
url: http://module-build.sourceforge.net/META-spec-v1.4.html
- version: 1.4
+ version: '1.4'
+name: Test-Database
+requires:
+ Carp: '0'
+ Cwd: '0'
+ DBD::DBM: '0'
+ DBI: '0'
+ File::HomeDir: '0'
+ File::Path: '0'
+ File::Spec: '0'
+ YAML::Tiny: '1.62'
+ perl: '5.006'
+ strict: '0'
+ version: '0'
+ warnings: '0'
+resources:
+ bugtracker: http://rt.cpan.org/NoAuth/Bugs.html?Dist=Test-Database
+ repository: http://github.com/book/Test-Database.git
+version: '1.112'
@@ -1,20 +1,82 @@
+
+# This file was automatically generated by Dist::Zilla::Plugin::MakeMaker v5.012.
use strict;
use warnings;
-use ExtUtils::MakeMaker;
-
-WriteMakefile(
- NAME => 'Test::Database',
- AUTHOR => 'Philippe Bruhat (BooK) <book@cpan.org>',
- VERSION_FROM => 'lib/Test/Database.pm',
- ABSTRACT_FROM => 'lib/Test/Database.pm',
- PL_FILES => {},
- PREREQ_PM => {
- 'Test::More' => 0,
- 'DBI' => 1,
- 'File::HomeDir' => 0.50,
- 'version' => 0,
- 'YAML::Tiny' => 1.27,
- },
- dist => { COMPRESS => 'gzip -9f', SUFFIX => 'gz', },
- clean => { FILES => 'Test-Database-*' },
+
+use 5.006;
+
+use ExtUtils::MakeMaker 6.30;
+
+
+
+my %WriteMakefileArgs = (
+ "ABSTRACT" => "Database handles ready for testing",
+ "AUTHOR" => "Philippe Bruhat (BooK) <book\@cpan.org>",
+ "BUILD_REQUIRES" => {},
+ "CONFIGURE_REQUIRES" => {
+ "ExtUtils::MakeMaker" => "6.30"
+ },
+ "DISTNAME" => "Test-Database",
+ "EXE_FILES" => [],
+ "LICENSE" => "perl",
+ "NAME" => "Test::Database",
+ "PREREQ_PM" => {
+ "Carp" => 0,
+ "Cwd" => 0,
+ "DBD::DBM" => 0,
+ "DBI" => 0,
+ "File::HomeDir" => 0,
+ "File::Path" => 0,
+ "File::Spec" => 0,
+ "YAML::Tiny" => "1.62",
+ "strict" => 0,
+ "version" => 0,
+ "warnings" => 0
+ },
+ "TEST_REQUIRES" => {
+ "File::Find" => 0,
+ "File::Temp" => 0,
+ "List::Util" => 0,
+ "SQL::Statement" => 0,
+ "Test::More" => "0.88"
+ },
+ "VERSION" => "1.112",
+ "test" => {
+ "TESTS" => "t/*.t"
+ }
+);
+
+
+my %FallbackPrereqs = (
+ "Carp" => 0,
+ "Cwd" => 0,
+ "DBD::DBM" => 0,
+ "DBI" => 0,
+ "File::Find" => 0,
+ "File::HomeDir" => 0,
+ "File::Path" => 0,
+ "File::Spec" => 0,
+ "File::Temp" => 0,
+ "List::Util" => 0,
+ "SQL::Statement" => 0,
+ "Test::More" => "0.88",
+ "YAML::Tiny" => "1.62",
+ "strict" => 0,
+ "version" => 0,
+ "warnings" => 0
);
+
+
+unless ( eval { ExtUtils::MakeMaker->VERSION(6.63_03) } ) {
+ delete $WriteMakefileArgs{TEST_REQUIRES};
+ delete $WriteMakefileArgs{BUILD_REQUIRES};
+ $WriteMakefileArgs{PREREQ_PM} = \%FallbackPrereqs;
+}
+
+delete $WriteMakefileArgs{CONFIGURE_REQUIRES}
+ unless eval { ExtUtils::MakeMaker->VERSION(6.52) };
+
+WriteMakefile(%WriteMakefileArgs);
+
+
+
@@ -0,0 +1,48 @@
+name = Test-Database
+author = Philippe Bruhat (BooK) <book@cpan.org>
+license = Perl_5
+copyright_holder = Philippe Bruhat (BooK)
+; copyright_year = 2008-2014
+
+[PkgVersion]
+
+[@Filter]
+-bundle = @Basic
+-remove = Readme
+
+[PruneFiles]
+filename = setup
+match = \.patch$
+match = mess/.*
+match = cover_db
+
+[AutoPrereqs]
+
+[Prereqs]
+YAML::Tiny = 1.62
+
+[ReportVersions::Tiny]
+
+[MetaResources]
+repository.web = http://github.com/book/Test-Database
+repository.url = http://github.com/book/Test-Database.git
+repository.type = git
+bugtracker.web = http://rt.cpan.org/NoAuth/Bugs.html?Dist=Test-Database
+bugtracker.mailto = bug-test-database@rt.cpan.org
+
+[MetaTests]
+[PodSyntaxTests]
+[PodCoverageTests]
+
+[NextRelease]
+format = %v %{EEE MMM d yyyy}d
+
+[@Git]
+changelog = Changes
+commit_msg = Changes for version %v
+tag_format = v%v
+tag_message = %N v%v
+push_to = origin
+push_to = github
+
+[Git::NextVersion]
@@ -1,4 +1,5 @@
package Test::Database::Driver::CSV;
+$Test::Database::Driver::CSV::VERSION = '1.112';
use strict;
use warnings;
@@ -40,7 +41,7 @@ Test::Database::Driver::CSV - A Test::Database driver for CSV
=head1 DESCRIPTION
-This module is the C<Test::Database> driver for C<DBD::CSV>.
+This module is the L<Test::Database> driver for L<DBD::CSV>.
=head1 SEE ALSO
@@ -1,4 +1,5 @@
package Test::Database::Driver::DBM;
+$Test::Database::Driver::DBM::VERSION = '1.112';
use strict;
use warnings;
@@ -41,7 +42,7 @@ Test::Database::Driver::DBM - A Test::Database driver for DBM
=head1 DESCRIPTION
-This module is the C<Test::Database> driver for C<DBD::DBM>.
+This module is the L<Test::Database> driver for L<DBD::DBM>.
=head1 SEE ALSO
@@ -1,4 +1,5 @@
package Test::Database::Driver::Pg;
+$Test::Database::Driver::Pg::VERSION = '1.112';
use strict;
use warnings;
use Carp;
@@ -64,7 +65,7 @@ Test::Database::Driver::Pg - A Test::Database driver for Pg
=head1 DESCRIPTION
-This module is the C<Test::Database> driver for C<DBD::Pg>.
+This module is the L<Test::Database> driver for L<DBD::Pg>.
=head1 EXTRA PARAMETERS
@@ -1,4 +1,5 @@
package Test::Database::Driver::SQLite;
+$Test::Database::Driver::SQLite::VERSION = '1.112';
use strict;
use warnings;
@@ -39,7 +40,7 @@ Test::Database::Driver::SQLite - A Test::Database driver for SQLite
=head1 DESCRIPTION
-This module is the C<Test::Database> driver for C<DBD::SQLite>.
+This module is the L<Test::Database> driver for L<DBD::SQLite>.
=head1 SEE ALSO
@@ -1,4 +1,5 @@
package Test::Database::Driver::SQLite2;
+$Test::Database::Driver::SQLite2::VERSION = '1.112';
use strict;
use warnings;
@@ -39,7 +40,7 @@ Test::Database::Driver::SQLite2 - A Test::Database driver for SQLite2
=head1 DESCRIPTION
-This module is the C<Test::Database> driver for C<DBD::SQLite2>.
+This module is the L<Test::Database> driver for L<DBD::SQLite2>.
=head1 SEE ALSO
@@ -1,4 +1,5 @@
package Test::Database::Driver::mysql;
+$Test::Database::Driver::mysql::VERSION = '1.112';
use strict;
use warnings;
@@ -51,6 +52,8 @@ sub databases {
__END__
+=encoding utf8
+
=head1 NAME
Test::Database::Driver::mysql - A Test::Database driver for mysql
@@ -62,7 +65,7 @@ Test::Database::Driver::mysql - A Test::Database driver for mysql
=head1 DESCRIPTION
-This module is the C<Test::Database> driver for C<DBD::mysql>.
+This module is the L<Test::Database> driver for L<DBD::mysql>.
=head1 SEE ALSO
@@ -74,8 +77,8 @@ Philippe Bruhat (BooK), C<< <book@cpan.org> >>
=head1 ACKNOWLEDGEMENTS
-Many thanks to Kristian Köhntopp who helped me while writing a
-previous version of this module (before C<Test::Database> 0.03).
+Many thanks to Kristian Köhntopp who helped me while writing a
+previous version of this module (before L<Test::Database> 0.03).
=head1 COPYRIGHT
@@ -1,4 +1,5 @@
package Test::Database::Driver;
+$Test::Database::Driver::VERSION = '1.112';
use strict;
use warnings;
use Carp;
@@ -58,8 +59,6 @@ sub new {
}
my $self = bless {
- username => '',
- password => '',
%args,
dbd => $class->name() || $args{dbd},
},
@@ -339,32 +338,38 @@ Test::Database::Driver - Base class for Test::Database drivers
=head1 DESCRIPTION
-C<Test::Database::Driver> is a base class for creating C<Test::Database>
+Test::Database::Driver is a base class for creating L<Test::Database>
drivers.
=head1 METHODS
The class provides the following methods:
-=over 4
+=head2 new
+
+ my $driver = Test::Database::Driver->new( driver => 'SQLite' );
-=item new( %args )
+ my $driver = Test::Database::Driver::SQLite->new();
-Create a new C<Test::Database::Driver> object.
+Create a new Test::Database::Driver object.
If called as C<< Test::Database::Driver->new() >>, requires a C<driver>
parameter to define the actual object class.
-=item make_handle()
+=head2 make_handle
-Create a new C<Test::Database::Handle> object, attached to an existing database
+ my $handle = $driver->make_handle();
+
+Create a new L<Test::Database::Handle> object, attached to an existing database
or to a newly created one.
The decision whether to create a new database or not is made by
-C<Test::Database::Driver> based on the information in the mapper.
+Test::Database::Driver based on the information in the mapper.
See L<TEMPORARY STORAGE ORGANIZATION> for details.
-=item make_dsn( %args )
+=head2 make_dsn
+
+ my $dsn = $driver->make_dsn( %args )
Return a Data Source Name based on the driver's DSN, with the key/value
pairs contained in C<%args> as additional parameters.
@@ -372,122 +377,146 @@ pairs contained in C<%args> as additional parameters.
This is typically used by C<dsn()> to make a DSN for a specific database,
based on the driver's DSN.
-=item name()
+=head2 name
-=item dbd()
+=head2 dbd
+
+ my $name = $driver->dbd;
The driver's short name (everything after C<Test::Database::Driver::>).
-=item base_dir()
+=head2 base_dir
+
+ my $dir = $driver->base_dir;
The directory where the driver should store all the files for its databases,
if needed. Typically used by file-based database drivers.
-=item version()
+=head2 version
+
+ my $db_version = $driver->version;
C<version> object representing the version of the underlying database enginge.
This object is build with the return value of C<_version()>.
-=item version_string()
+=head2 version_string
+
+ my $db_version = $driver->version_string;
Version string representing the version of the underlying database enginge.
This string is the actual return value of C<_version()>.
-=item dbd_version()
+=head2 dbd_version
+
+ my $dbd_version = $driver->dbd_version;
The version of the DBD used to connect to the database engine, as returned
by C<VERSION()>.
-=item driver_dsn()
+=head2 driver_dsn
+
+ my $dsn = $driver->driver_dsn;
Return a driver Data Source Name, sufficient to connect to the database
engine without specifying an actual database.
-=item username()
+=head2 username
+
+ my $username = $driver->username;
+
+Return the connection username. Defaults to C<undef>.
-Return the connection username.
+=head2 password
-=item password()
+ my $password = $driver->password;
-Return the connection password.
+Return the connection password. Defaults to C<undef>.
-=item connection_info()
+=head2 connection_info()
+
+ my @info = $driver->connection_info;
Return the connection information triplet (C<driver_dsn>, C<username>,
C<password>).
-=item version_matches( $request )
+=head2 version_matches
+
+ if ( $driver->version_matches($request) ) {
+ ...;
+ }
Return a boolean indicating if the driver's version matches the version
constraints in the given request (see L<Test::Database> documentation's
section about requests).
-=back
+=head1 METHODS FOR DRIVER AUTHORS
The class also provides a few helpful commands that may be useful for driver
authors:
-=over 4
+=head2 available_dbname
-=item available_dbname()
+ my $dbname = $self->available_dbname();
Return an unused database name that can be used to create a new database
for the driver.
-=item dsn( $dbname )
+=head2 dsn
-Build a Data Source Name for the database with the given C<$dbname>,
-based on the driver's DSN.
+ my $dns = $self->dsn( $dbname )
-=back
+Build a Data Source Name for the database with the given C<$dbname>,
+based on the driver's DSN.
=head1 WRITING A DRIVER FOR YOUR DATABASE OF CHOICE
The L<SYNOPSIS> contains a good template for writing a
-C<Test::Database::Driver> class.
+Test::Database::Driver class.
Creating a driver requires writing the following methods:
-=over 4
+=head2 _version
-=item _version()
+ my $version = $driver->_version;
Return the version of the underlying database engine.
-=item create_database( $name )
+=head2 create_database
+
+ $driver->create_database( $name );
Create the database for the corresponding DBD driver.
-Return a C<Test::Database::Handle> in case of success, and nothing in
+Return a L<Test::Database::Handle> in case of success, and nothing in
case of failure to create the database.
-=item drop_database( $name )
+=head2 drop_database( $name )
+
+ $driver->drop_database( $name );
Drop the database named C<$name>.
-=back
+=head1 OVERRIDABLE METHODS WHEN WRITING A DRIVER
-Some methods have defaults implementations in C<Test::Database::Driver>,
+Some methods have defaults implementations in Test::Database::Driver,
but those can be overridden in the derived class:
-=over 4
-
-=item is_filebased()
+=head2 is_filebased
Return a boolean value indicating if the database engine is file-based
or not, i.e. if all the database information is stored in a file or a
directory, and no external database server is needed.
-=item databases()
+=head2 databases
+
+ my @db = $driver->databases();
Return the names of all existing databases for this driver as a list
(the default implementation is only valid for file-based drivers).
-=back
-
=head1 TEMPORARY STORAGE ORGANIZATION
-Subclasses of C<Test::Database::Driver> store useful information
+Subclasses of Test::Database::Driver store useful information
in the system's temporary directory, under a directory named
F<Test-Database-$user> (C<$user> being the current user's name).
@@ -498,7 +527,7 @@ That directory contains the following files:
=item database files
The database files and directories created by file-based drivers
-controlled by C<Test::Database> are stored here, under names matching
+controlled by L<Test::Database> are stored here, under names matching
F<tdd_B<DRIVER>_B<N>>, where B<DRIVER> is the lowercased name of the
driver and B<N> is a number.
@@ -506,7 +535,7 @@ driver and B<N> is a number.
A YAML file containing a C<cwd()> / database name mapping, to enable a
given test suite to receive the same database handles in all the test
-scripts that call the C<Test::Database->handles()> method.
+scripts that call the C<< Test::Database->handles() >> method.
=back
@@ -1,4 +1,5 @@
package Test::Database::Handle;
+$Test::Database::Handle::VERSION = '1.112';
use strict;
use warnings;
use Carp;
@@ -21,8 +22,6 @@ sub new {
# fix args
%args = (
- username => '',
- password => '',
%args,
dbd => $driver,
);
@@ -65,50 +64,51 @@ Test::Database::Handle - A class for Test::Database handles
=head1 DESCRIPTION
-C<Test::Database::Handle> is a very simple class for encapsulating the
+Test::Database::Handle is a very simple class for encapsulating the
information about a test database handle.
-C<Test::Database::Handle> objects are used within a test script to
+Test::Database::Handle objects are used within a test script to
obtain the necessary information about a test database handle.
Handles are obtained through the C<< Test::Database->handles() >>
or C<< Test::Database->handle() >> methods.
=head1 METHODS
-C<Test::Database::Handle> provides the following methods:
+Test::Database::Handle provides the following methods:
-=over 4
+=head2 new
-=item new( %args )
-
-Return a new C<Test::Database::Handle> with the given parameters
+Return a new Test::Database::Handle with the given parameters
(C<dsn>, C<username>, C<password>).
The only mandatory argument is C<dsn>.
-=back
+=head1 ACCESSORS
The following accessors are available.
-=over 4
-
-=item dsn()
+=head2 dsn
Return the Data Source Name.
-=item username()
+=head2 username
-Return the connection username.
+Return the connection username. Defaults to C<undef>.
-=item password()
+=head2 password
-Return the connection password.
+Return the connection password. Defaults to C<undef>.
-=item connection_info()
+=head2 connection_info
Return the connection information triplet (C<dsn>, C<username>, C<password>).
-=item dbh( [ $attr ] )
+ my ( $dsn, $username, $password ) = $handle->connection_info;
+
+=head2 dbh
+
+ my $dbh = $handle->dbh;
+ my $dbh = $handle->dbh( $attr );
Return the DBI database handle obtained when connecting with the
connection triplet returned by C<connection_info()>.
@@ -116,19 +116,17 @@ connection triplet returned by C<connection_info()>.
The optional parameter C<$attr> is a reference to a hash of connection
attributes, passed directly to DBI's C<connect()> method.
-=item name()
+=head2 name
Return the database name attached to the handle.
-=item dbd()
+=head2 dbd
Return the DBI driver name, as computed from the C<dsn>.
-=item driver()
-
-Return the C<Test::Database::Driver> object attached to the handle.
+=head2 driver
-=back
+Return the L<Test::Database::Driver> object attached to the handle.
=head1 AUTHOR
@@ -4,7 +4,7 @@ Test::Database::Tutorial - How to use Test::Database
=head1 INTRODUCTION
-The goal of the C<Test::Database> module is to provide easy to use test
+The goal of the L<Test::Database> module is to provide easy to use test
databases for test scripts that need them.
=head2 The problem
@@ -54,7 +54,7 @@ be at risk!
=back
-=head2 A solution: C<Test::Database>
+=head2 A solution: L<Test::Database>
Many modules use a database to store their data, and often support
several database engines.
@@ -62,7 +62,7 @@ several database engines.
Wouldn't it be nice to be able to test on all the supported databases
that are available on the test system? Without breaking (into) anything?
-This is the goal of the C<Test::Database> module. It supports:
+This is the goal of the L<Test::Database> module. It supports:
=over 4
@@ -76,28 +76,28 @@ automatic detection of "file-based" database engines (typically, SQLite).
=back
-The rest of this document describes various use cases for C<Test::Database>.
+The rest of this document describes various use cases for L<Test::Database>.
=head1 MODULE AND TEST AUTHOR
-C<Test::Database> has a single interface for test authors:
+L<Test::Database> has a single interface for test authors:
my @handles = Test::Database->handles( @requests );
C<@request> is a list of "requests" for databases handles. Requests
must declare the DBD they expect, and can optionaly add version-based
-limitations (only available for drivers supported by C<Test::Database>).
+limitations (only available for drivers supported by L<Test::Database>).
-The handles returned are objects of the C<Test::Database::Handle> class.
+The handles returned are objects of the L<Test::Database::Handle> class.
The data contained in the database is never destroyed or cleaned
-up by C<Test::Database>, so it's perfectly fine to have a startup script
+up by L<Test::Database>, so it's perfectly fine to have a startup script
that will setup the necessary tables and test data, several tests scripts
that will build and update the data, and a eventually a teardown script
that will drop all created tables.
-C<Test::Database> can return two types of databases handles:
+L<Test::Database> can return two types of databases handles:
=over 4
@@ -118,7 +118,7 @@ In any case, the database is assumed to provide C<DROP TABLE> and
C<CREATE TABLE> rights, and the test script is by definition allowed
to do whatever it pleases with the tables that exist in the database.
-Note that C<Test::Database> supports any DSN, not just those for which
+Note that L<Test::Database> supports any DSN, not just those for which
it has a driver. If your module supports Oracle, you can add C<'Oracle'>
to your list of requests, and if the host owner configured a C<dsn>
pointing at an Oracle database, then it will be available for your tests.
@@ -159,11 +159,11 @@ A typical F<~/.test-database> configuration file would look like this:
dsn = dbi:Oracle:test
There is no need to add C<dsn> sections for file-based drivers
-(at least the ones that have a corresponding C<Test::Database::Driver>),
+(at least the ones that have a corresponding L<Test::Database::Driver>),
since the module will automatically detect the available ones and create
databases as needed.
-To find out which of the DBD that C<Test::Database> supports are
+To find out which of the DBD that L<Test::Database> supports are
installed, use the following one-liner:
$ perl -MTest::Database -le 'print for Test::Database->list_drivers("available")'
@@ -180,10 +180,10 @@ With no parameter, it will return the list of configured ones:
=head1 CPAN TESTER
-The main goal of C<Test::Database> from the point of view of a tester
+The main goal of L<Test::Database> from the point of view of a tester
is: "configure once, test everything".
-As a CPAN tester, once you have installed C<Test::Database>, you
+As a CPAN tester, once you have installed L<Test::Database>, you
should edit the local equivalent of F<~/.test-database> for the
user that will be running the CPAN test suites.
@@ -195,12 +195,12 @@ requests it.
C<driver_dsn> sections define the information needed to connect to a
database engine (a "driver") with sufficient rights to run a
-C<CREATE DATABASE> command. This allows C<Test::Database> to create the
+C<CREATE DATABASE> command. This allows L<Test::Database> to create the
databases on demand, thus ensuring every test suite will get a specific
database.
If you have file-based database engine, there is nothing to setup, as
-C<Test::Database> is able to detect available file-based engines and
+L<Test::Database> is able to detect available file-based engines and
use them as needed.
Other database engines like C<mysql> and C<Pg> require a little more
@@ -222,27 +222,27 @@ If you have a large scale testing setup, you may want to setup a single
MySQL or Postgres instance for all your test hosts, rather than one per
test host.
-Databases created by C<Test::Database::Driver> (using a configured
+Databases created by L<Test::Database::Driver> (using a configured
C<driver_dsn> have a name built after the following template:
C<tdd_I<driver>_I<login>_I<n>>, where I<driver> is the DBD name, I<login>
-is the login of the user running C<Test::Database> and I<n> a number that
+is the login of the user running L<Test::Database> and I<n> a number that
If the same database server is used by several host running
-C<Test::Database> from the same user account, there is a race condition
+L<Test::Database> from the same user account, there is a race condition
during with two different host may try to create the a database with
the same name. A simple trick to avoid this is to add a C<key> section
to the F<~/.test-database> configuration file.
-If the C<key> entry exists, the template used by C<Test::Database::Driver>
+If the C<key> entry exists, the template used by L<Test::Database::Driver>
to create new databases is C<tdd_I<driver>_I<login>_I<key>_I<n>>.
=head2 Cleaning the test drivers
-When given a C<driver_dsn>, C<Test::Database> will use it to create a
+When given a C<driver_dsn>, L<Test::Database> will use it to create a
database for each test suite that requests one. Some mapping information
is created to ensure the same test suite always receives a handle to
the same database. (The mapping of test suite to database is based on
-the current working directory when C<Test::Database> is loaded).
+the current working directory when L<Test::Database> is loaded).
After a while, your database engine may fill up with unused test databases.
@@ -253,7 +253,7 @@ file-based drivers store their database files in the system's temporary
directory too).
The following one-liner will list all the existing databases that were
-created by C<Test::Database> in your configured drivers:
+created by L<Test::Database> in your configured drivers:
perl -MTest::Database -le 'print join "\n ", $_->name, $_->databases for Test::Database->drivers'
@@ -281,22 +281,22 @@ corresponding to that key will be dropped.
=head1 ADDING SUPPORT FOR A NEW DATABASE ENGINE
-C<Test::Database> currently supports the following DBD drivers:
+L<Test::Database> currently supports the following DBD drivers:
C<CSV>, C<DBM>, C<mysql>, C<Pg>, C<SQLite2>, C<SQLite>.
Adding a new driver requires writing a corresponding
-C<Test::Database::Driver> subclass, having the same name as the original
+L<Test::Database::Driver> subclass, having the same name as the original
C<DBD> driver.
An example module is provided in F<eg/MyDriver.pm>, and the other
drivers can also be used as an example. See also the I<WRITING A
DRIVER FOR YOUR DATABASE OF CHOICE> section in the documentation for
-C<Test::Database::Driver>.
+L<Test::Database::Driver>.
=head1 WHERE DO DSN COME FROM?
-The following ASCII-art graph shows where the C<Test::Database::Handle>
+The following ASCII-art graph shows where the L<Test::Database::Handle>
objects returned by the C<handles()> method come from:
@@ -322,32 +322,32 @@ Here are a few details about the C<handles()> method works:
=item *
-C<Test::Database> maintains a list of C<Test::Database::Handle> objects
+L<Test::Database> maintains a list of L<Test::Database::Handle> objects
computed from the DSN listed in the configuration.
The handles matching the request are selected.
=item *
-C<Test::Database> also maintains a list of C<Test::Database::Driver>
+L<Test::Database> also maintains a list of L<Test::Database::Driver>
objects computed from the list of supported file-based drivers that are
locally available and from the list in the configuration file.
The list of matching drivers is computed from the requests. Each driver
is then requested to provide an existing database (using its existing
mapping information) or to create one if needed, and returns the
-corresponding C<Test::Database::Handle> objects.
+corresponding L<Test::Database::Handle> objects.
=item *
-Finally, all the collected C<Test::Database::Handle> objects are returned.
+Finally, all the collected L<Test::Database::Handle> objects are returned.
=back
-So, without any configuration, C<Test::Database> will only be able to
+So, without any configuration, L<Test::Database> will only be able to
provide file-based databases. It is also recommended to B<not> put DSN
or driver information for the file-based database engines that have
-a corresponding C<Test::Database::Driver> class, since it will cause
+a corresponding L<Test::Database::Driver> class, since it will cause
C<handles()> to return several handles for the same database engine.
=head1 AUTHOR
@@ -1,4 +1,5 @@
package Test::Database::Util;
+$Test::Database::Util::VERSION = '1.112';
use strict;
use warnings;
use Carp;
@@ -63,24 +64,22 @@ Test::Database::Util - Utility functions for Test::Database modules
=head1 DESCRIPTION
-C<Test::Database::Util> exports a collection of functions used by
+Test::Database::Util exports a collection of functions used by
several modules in the C<Test-Database> distribution.
=head1 EXPORTED FUNCTIONS
-All functions provided by C<Test::Database::Util> are exported in the
+All functions provided by Test::Database::Util are exported in the
calling package.
The following functions are provided:
-=over 4
+=head2 _read_file
-=item _read_file( $file )
+ _read_file( $file )
Return a list of hash references, read in the given C<$file> file.
-=back
-
=head1 AUTHOR
Philippe Bruhat (BooK), C<< <book@cpan.org> >>
@@ -1,4 +1,5 @@
package Test::Database;
+$Test::Database::VERSION = '1.112';
use 5.006;
use warnings;
use strict;
@@ -12,8 +13,6 @@ use Test::Database::Util;
use Test::Database::Driver;
use Test::Database::Handle;
-our $VERSION = '1.11';
-
#
# global configuration
#
@@ -61,14 +60,20 @@ sub load_drivers {
# startup configuration
__PACKAGE__->load_drivers();
-__PACKAGE__->load_config() if -e _rcfile();
+__PACKAGE__->load_config();
#
# private functions
#
# location of our resource file
sub _rcfile {
- File::Spec->catfile( File::HomeDir->my_data(), '.test-database' );
+ my $basename = '.test-database';
+ my $rc = File::Spec->catfile( File::HomeDir->my_home(), $basename );
+ return $rc if -e $rc;
+
+ # while transitioning to the new scheme, give the old name if it exists
+ my $old = File::Spec->catfile( File::HomeDir->my_data(), $basename );
+ return -e $old ? $old : $rc;
}
#
@@ -81,7 +86,7 @@ sub clean_config {
sub load_config {
my ( $class, @files ) = @_;
- @files = ( _rcfile() ) if !@files;
+ @files = grep -e, _rcfile() if !@files;
# fetch the items (dsn, driver_dsn) from the config files
my @items = map { _read_file($_) } @files;
@@ -228,80 +233,75 @@ test databases over several test scripts.
=head1 DESCRIPTION
-Quoting Michael Schwern:
-
-I<There's plenty of modules which need a database, and they all have
-to be configured differently and they're always a PITA when you first
-install and each and every time they upgrade.>
-
-I<User setup can be dealt with by making Test::Database a build
-dependency. As part of Test::Database's install process it walks the
-user through the configuration process. Once it's done, it writes out
-a config file and then it's done for good.>
-
-See L<http://www.nntp.perl.org/group/perl.qa/2008/10/msg11645.html>
-for the thread that led to the creation of C<Test::Database>.
-
-C<Test::Database> provides a simple way for test authors to request
+Test::Database provides a simple way for test authors to request
a test database, without worrying about environment variables or the
test host configuration.
See L<SYNOPSIS> for typical usage.
+See L<Test::Database::Tutorial> for more detailed explanations.
+
=head1 METHODS
-C<Test::Database> provides the following methods:
+Test::Database provides the following methods:
-=over 4
+=head2 list_drivers
-=item list_drivers( [$type] )
+ my @drivers = Test::Database->list_drivers();
+ my @drivers = Test::Database->list_drivers('available');
Return a list of driver names of the given "type".
-C<all> returns the list of all existing C<Test::Database::Driver> subclasses.
+C<all> returns the list of all existing L<Test::Database::Driver> subclasses.
-C<available> returns the list of C<Test::Database::Driver> subclasses for which the matching
+C<available> returns the list of L<Test::Database::Driver> subclasses for which the matching
C<DBD> class is available.
Called with no parameter (or anything not matching C<all> or C<available>), it will return
the list of currently loaded drivers.
-=item drivers()
+=head2 drivers
-Returns the C<Test::Database::Driver> instances that are setup by
+Returns the L<Test::Database::Driver> instances that are setup by
C<load_drivers()> and updated by C<load_config()>.
-=item load_drivers()
+=head2 load_drivers
Load the available drivers from the system (file-based drivers, usually).
-=item load_config( @files )
+=head2 load_config
+
+ Test::Database->load_config($config);
Read configuration from the files in C<@files>.
If no file is provided, the local equivalent of F<~/.test-database> is used.
-=item clean_config()
+=head2 clean_config
+
+ Test::Database->clean_config();
Empties whatever configuration has already been loaded.
Also removes the loaded drivers list.
-=item handles( @requests )
+=head2 handles
-Return a set of C<Test::Database::Handle> objects that match the
+ my @handles = Test::Database->handles(@requests);
+
+Return a set of L<Test::Database::Handle> objects that match the
given C<@requests>.
If C<@requests> is not provided, return all the available handles.
See L<REQUESTS> for details about writing requests.
-=item handle( @request )
+=head2 handle
+
+ my $handle = Test::Database->handle(@requests);
I<Singular> version of C<handles()>, that returns the first matching
handle.
-=back
-
=head1 REQUESTS
The C<handles()> method takes I<requests> as parameters. A request is
@@ -372,7 +372,7 @@ C<dsn>, C<driver_dsn> or C<key> keys being used to split successive entries:
driver_dsn = dbi:mysql:
username = root
-The C<username> and C<password> keys are optional and empty strings will be
+The C<username> and C<password> keys are optional and C<undef> will be
used if they are not provided.
Empty lines and comments are ignored.
@@ -383,7 +383,7 @@ allows several hosts to share access to the same database server
without risking a race condition when creating a new database. See
L<Test::Database::Tutorial> for a longer explanation.
-Individual drivers may accept extra parameters. See their documetation
+Individual drivers may accept extra parameters. See their documentation
for details. Unrecognized parameters and not used, and therefore ignored.
=head1 AUTHOR
@@ -437,11 +437,27 @@ write the F<.test-database> configuration file.
=back
+=head1 HISTORY
+
+Quoting Michael Schwern:
+
+I<There's plenty of modules which need a database, and they all have
+to be configured differently and they're always a PITA when you first
+install and each and every time they upgrade.>
+
+I<User setup can be dealt with by making Test::Database a build
+dependency. As part of Test::Database's install process it walks the
+user through the configuration process. Once it's done, it writes out
+a config file and then it's done for good.>
+
+See L<http://www.nntp.perl.org/group/perl.qa/2008/10/msg11645.html>
+for the thread that led to the creation of Test::Database.
+
=head1 ACKNOWLEDGEMENTS
Thanks to C<< <perl-qa@perl.org> >> for early comments.
-Thanks to Nelson Ferraz for writing C<DBIx::Slice>, the testing of
+Thanks to Nelson Ferraz for writing L<DBIx::Slice>, the testing of
which made me want to have a generic way to obtain a test database.
Thanks to Mark Lawrence for discussing this module with me, and
@@ -4,13 +4,15 @@ use Test::More;
use File::Find;
my @modules;
-find( sub { push @modules, $File::Find::name if /\.pm$/ }, 'blib/lib' );
+find( sub { push @modules, $File::Find::name if /\.pm$/ }, 'lib' );
plan tests => scalar @modules;
-use_ok($_)
- for reverse sort map { s!/!::!g; s/\.pm$//; s/^blib::lib:://; $_ }
- @modules;
-
-diag("Tested Test::Database $Test::Database::VERSION, Perl $], $^X");
+@modules = reverse sort map { s!/!::!g; s/\.pm$//; s/^lib:://; $_ } @modules;
+# load in isolation
+local $ENV{PERL5LIB} = join $Config::Config{path_sep} || ';', @INC;
+for my $module (@modules) {
+ `$^X -M$module -e1`;
+ is( $? >> 8, 0, "perl -M$module -e1" );
+}
@@ -0,0 +1,90 @@
+use strict;
+use warnings;
+use Test::More 0.88;
+# This is a relatively nice way to avoid Test::NoWarnings breaking our
+# expectations by adding extra tests, without using no_plan. It also helps
+# avoid any other test module that feels introducing random tests, or even
+# test plans, is a nice idea.
+our $success = 0;
+END { $success && done_testing; }
+
+# List our own version used to generate this
+my $v = "\nGenerated by Dist::Zilla::Plugin::ReportVersions::Tiny v1.08\n";
+
+eval { # no excuses!
+ # report our Perl details
+ my $want = '5.006';
+ $v .= "perl: $] (wanted $want) on $^O from $^X\n\n";
+};
+defined($@) and diag("$@");
+
+# Now, our module version dependencies:
+sub pmver {
+ my ($module, $wanted) = @_;
+ $wanted = " (want $wanted)";
+ my $pmver;
+ eval "require $module;";
+ if ($@) {
+ if ($@ =~ m/Can't locate .* in \@INC/) {
+ $pmver = 'module not found.';
+ } else {
+ diag("${module}: $@");
+ $pmver = 'died during require.';
+ }
+ } else {
+ my $version;
+ eval { $version = $module->VERSION; };
+ if ($@) {
+ diag("${module}: $@");
+ $pmver = 'died during VERSION check.';
+ } elsif (defined $version) {
+ $pmver = "$version";
+ } else {
+ $pmver = '<undef>';
+ }
+ }
+
+ # So, we should be good, right?
+ return sprintf('%-45s => %-10s%-15s%s', $module, $pmver, $wanted, "\n");
+}
+
+eval { $v .= pmver('Carp','any version') };
+eval { $v .= pmver('Cwd','any version') };
+eval { $v .= pmver('DBD::DBM','any version') };
+eval { $v .= pmver('DBI','any version') };
+eval { $v .= pmver('ExtUtils::MakeMaker','6.30') };
+eval { $v .= pmver('File::Find','any version') };
+eval { $v .= pmver('File::HomeDir','any version') };
+eval { $v .= pmver('File::Path','any version') };
+eval { $v .= pmver('File::Spec','any version') };
+eval { $v .= pmver('File::Temp','any version') };
+eval { $v .= pmver('List::Util','any version') };
+eval { $v .= pmver('Pod::Coverage::TrustPod','any version') };
+eval { $v .= pmver('SQL::Statement','any version') };
+eval { $v .= pmver('Test::CPAN::Meta','any version') };
+eval { $v .= pmver('Test::More','0.88') };
+eval { $v .= pmver('Test::Pod','1.41') };
+eval { $v .= pmver('Test::Pod::Coverage','1.08') };
+eval { $v .= pmver('YAML::Tiny','1.62') };
+eval { $v .= pmver('strict','any version') };
+eval { $v .= pmver('version','0.9901') };
+eval { $v .= pmver('warnings','any version') };
+
+
+# All done.
+$v .= <<'EOT';
+
+Thanks for using my code. I hope it works for you.
+If not, please try and include this output in the bug report.
+That will help me reproduce the issue and solve your problem.
+
+EOT
+
+diag($v);
+ok(1, "we really didn't test anything, just reporting data");
+$success = 1;
+
+# Work around another nasty module on CPAN. :/
+no warnings 'once';
+$Template::Test::NO_FLUSH = 1;
+exit 0;
@@ -11,8 +11,8 @@ my @tests = (
[ [ dbd => 'Zlonk' ], undef, qr/^dsn argument required/ ],
[ [ driver => 'Foo', dsn => 'dbi:SQLite:dbname=zlonk' ],
{ dsn => 'dbi:SQLite:dbname=zlonk',
- username => '',
- password => '',
+ username => undef,
+ password => undef ,
dbd => 'SQLite',
driver => 'Foo',
}
@@ -22,8 +22,8 @@ my @tests = (
name => 'zlonk'
],
{ dsn => 'dbi:SQLite:dbname=zlonk',
- username => '',
- password => '',
+ username => undef,
+ password => undef,
dbd => 'SQLite',
name => 'zlonk',
}
@@ -33,7 +33,7 @@ my $handle = Test::Database::Handle->new( dsn => $dsn );
is_deeply(
[ $handle->connection_info() ],
- [ $dsn, '', '' ],
+ [ $dsn, undef, undef ],
'connection_info()'
);
isa_ok( my $dbh2 = $handle->dbh(), 'DBI::db' );
@@ -15,7 +15,7 @@ my @drivers = (
} Test::Database->drivers()
);
-plan tests => 5 + @drivers * ( 1 + 2 * 12 ) + 2;
+plan tests => 5 + @drivers * ( 1 + 2 * 10 ) + 2;
my $base = 'Test::Database::Driver';
@@ -84,8 +84,9 @@ for my $args (@drivers) {
# driver_dsn, username, password, connection_info
ok( $driver->driver_dsn(), "$desc has a driver_dsn()" );
- ok( defined $driver->username(), "$desc has a username()" );
- ok( defined $driver->password(), "$desc has a password()" );
+ # skip these now that username and password default to undef
+ #ok( defined $driver->username(), "$desc has a username()" );
+ #ok( defined $driver->password(), "$desc has a password()" );
is_deeply(
[ $driver->connection_info() ],
[ map { $driver->$_ } qw< driver_dsn username password > ],
@@ -3,15 +3,6 @@ use warnings;
use Test::More;
use File::Spec;
-# DBD::DBM uses SQL::Statement if available
-# but SQL::Statement versions > 1.20 make the test fail
-# (see RT #56463, #56561)
-BEGIN {
- if ( eval { require SQL::Statement; $SQL::Statement::VERSION > 1.20; } ) {
- $ENV{DBI_SQL_NANO} = 1;
- }
-}
-
use Test::Database;
my @drivers = Test::Database->drivers();
@@ -20,6 +11,22 @@ my @drivers = Test::Database->drivers();
grep { $name eq $_ } @ARGV
} @drivers if @ARGV;
+# DBD::DBM uses SQL::Statement if available
+# but SQL::Statement versions > 1.20 make the test fail
+# (see RT #56463, #56561)
+if (eval {
+ require SQL::Statement;
+ diag "SQL::Statement $SQL::Statement::VERSION";
+ $SQL::Statement::VERSION > 1.20;
+ }
+ )
+{
+ my $skip_DBM = 0;
+ @drivers = grep { !( $_->name() eq 'DBM' and $skip_DBM = 1 ) } @drivers;
+ diag "skipping DBM tests because of SQL::Statement bug"
+ if $skip_DBM;
+}
+
plan skip_all => 'No drivers available for testing' if !@drivers;
# some SQL statements to try out
@@ -0,0 +1,16 @@
+#!perl
+
+BEGIN {
+ unless ($ENV{RELEASE_TESTING}) {
+ require Test::More;
+ Test::More::plan(skip_all => 'these tests are for release candidate testing');
+ }
+}
+
+# This file was automatically generated by Dist::Zilla::Plugin::MetaTests.
+
+use Test::More;
+
+eval "use Test::CPAN::Meta";
+plan skip_all => "Test::CPAN::Meta required for testing META.yml" if $@;
+meta_yaml_ok();
@@ -0,0 +1,22 @@
+#!perl
+
+BEGIN {
+ unless ($ENV{RELEASE_TESTING}) {
+ require Test::More;
+ Test::More::plan(skip_all => 'these tests are for release candidate testing');
+ }
+}
+
+# This file was automatically generated by Dist::Zilla::Plugin::PodCoverageTests.
+
+use Test::More;
+
+eval "use Test::Pod::Coverage 1.08";
+plan skip_all => "Test::Pod::Coverage 1.08 required for testing POD coverage"
+ if $@;
+
+eval "use Pod::Coverage::TrustPod";
+plan skip_all => "Pod::Coverage::TrustPod required for testing POD coverage"
+ if $@;
+
+all_pod_coverage_ok({ coverage_class => 'Pod::Coverage::TrustPod' });
@@ -0,0 +1,16 @@
+#!perl
+
+BEGIN {
+ unless ($ENV{RELEASE_TESTING}) {
+ require Test::More;
+ Test::More::plan(skip_all => 'these tests are for release candidate testing');
+ }
+}
+
+# This file was automatically generated by Dist::Zilla::Plugin::PodSyntaxTests.
+use Test::More;
+
+eval "use Test::Pod 1.41";
+plan skip_all => "Test::Pod 1.41 required for testing POD" if $@;
+
+all_pod_files_ok();