Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Aug 14, 2015
  1. Correct the call to all_synopsis_ok()

    For some reason, it was being passed invalid params...
Commits on Jul 20, 2015
Commits on Feb 9, 2015
  1. Whitespace: remove trailing whitespace & add spaces after commas

    Also, rename the _run_closure method to _run_subprocess.
Commits on Feb 6, 2015
  1. Only run the extra tests when we definately want them run.

    The main difference is that those tests should NOT run at uncontrolled
    times. For example, when someone is trying to build a debian package.
  2. Move xt/author tests into the main testing directory.

    ..and standardise them slightly.
  3. Update copyright year...

  4. Spellcheck

    Who would have thought it?
Commits on Dec 10, 2014
  1. Remove the 'use 5.6.2' from the modules

    It gives warnings (something about an invalid v-string) in some
    versions of perl.
Commits on Dec 7, 2014
  1. Don't require the use of Test::Warnings.

    Test::Warnings is not core, and I don't want to require too manay
Commits on Dec 2, 2014
  1. Merge pull request #3 from nfg/master

    Avoid undefined warning for empty files in all_pl_files
  2. Avoid undefined warning for empty files in all_pl_files

    Nigel Gregoire authored
Commits on Aug 11, 2014
  1. Fix CPAN test failure

    Before perl 5.8, there was no such thing as '-t'.
Commits on Aug 8, 2014
  1. Release 1.2.0

Commits on Jul 31, 2014
  1. rt83917: Not all files without an extension are perl files

    Only those with a perl looking shebang line should be treated
    as perl
Commits on Jul 17, 2014
  1. Correct the dependancy information

    Test::Compile actually requires:
    * File::Spec (core since 5.4.5)
    * Test::Builder (core since 5.6.2)
    * UIVERSAL::require (not core)
    * version (core since 5.6.9)
    It is now documented as requiring:
    * Perl 5.6.2 (includes File::Spec & Test::Builder)
    * UIVERSAL::require (not core)
    * version (core since 5.6.9)
  2. Default to being verbose

    Previously, Test::Compile was verbose, but Test::Compile::Internal
    was not.
Commits on Jul 16, 2014
  1. Promote the OO interface

    This involves:
    * Having a 'new' method in Test::Compile which actually creates a
      Test::Compile::Internal object
    * Updating the Test::Compile POD to include all the methods provided
      by the Test::Compile::Internal object
Commits on Mar 27, 2014
  1. Update copyright year

    Does this ever matter?
Commits on Mar 21, 2014
  1. Suppress the output during testing

    During testing, we only care about the result - we don't want any
Commits on Mar 19, 2014
  1. Fix broken distribution

    I added a file to the distribution, but forgot about the MANIFEST
Commits on Mar 18, 2014
  1. Remove the 'no_diag' logic

    Not because it is a bad idea, but because there is already a 'verbose'
    method to do essentailly the same thing
Commits on Mar 17, 2014
  1. Merge branch 'semver'

Commits on Mar 14, 2014
  1. Release engineering

  2. @schwern

    Add diagnostics on compilation failure.

    schwern authored
    Now you can know why it failed!  Makes heisenbugs so much easier to
    track down.
  3. @schwern

    require, don't use.

    schwern authored
    Test::Compile tests that modules compile, it should not be running any
    code.  This includes import routines.  It's not about testing pragmas.
    And some modules have wacky import routines that might not work
    without special setup or arguments.
    This also avoids problems with things like pm_file_ok("path/to/Some/")
    which would try "use path::to::Some::Module" rather than "use Some::Module" and
    try to call "path::to::Some::Module->import".
    Also, it's more robust to check the return value of require than to
    check for $@.
  4. @schwern

    Test for truth, not an integer.

    schwern authored
    False is not always 0, it could be '' or undef.  Truth is not always 1.
    It is more robust to use ok() than is() to test for truth.
  5. @schwern

    Small POD fix

    schwern authored
    I don't know if it's valid POD or not to cram two POD tags together,
    but it makes emacs unhappy.
  6. @schwern
Commits on Feb 22, 2013
  1. Use semantic versioning

    Still not sure about the appropriate version though!
Commits on Jan 22, 2013
  1. Release Engineeriing for 0.23

Something went wrong with that request. Please try again.