Permalink
Commits on Jun 14, 2016
  1. Merge pull request #50 from chriscool/chriscool-add-ipfs-update

    chriscool committed Jun 14, 2016
    Add ipfs-update among projects using Sharness
  2. Merge pull request #52 from stefanbeller/patch-1

    chriscool committed Jun 14, 2016
    Update upstream URL
  3. Update upstream URL

    stefanbeller committed Jun 14, 2016
  4. sharness: v1.0.0

    chriscool committed Jun 14, 2016
  5. Merge pull request #51 from chriscool/release-1.0

    chriscool committed Jun 14, 2016
    CHANGELOG: add release notes for Sharness 1.0
Commits on Dec 13, 2015
Commits on Oct 3, 2015
  1. Merge branch 'interactive-tests' of https://github.com/seveas/sharness

    chriscool committed Oct 3, 2015
    …into seveas-interactive-tests
Commits on Sep 28, 2015
  1. Merge pull request #49 from mlafeldt/sourcing-return-code-2

    chriscool committed Sep 28, 2015
    sharness: properly ensure it ends with code 0
Commits on Sep 27, 2015
  1. sharness: properly ensure it ends with code 0

    chriscool committed Sep 21, 2015
    It is better to have a `:` that ensures the script
    ends with code 0, rather than rely on the previous
    command.
Commits on Sep 21, 2015
  1. Support interactive tests

    seveas committed Sep 17, 2015
    sharness redirects /dev/null to stdin for tests to make sure individual
    tests accidently requiring input cannot hang the current test. However,
    sometimes you just need to test an interactive program (for example,
    when testing TOTP-based functionality). This patch lets you mark such
    tests with the INTERACTIVE prereq and adds an --interactive-tests
    argument to sharness.sh that will run those and will not redirect
    /dev/null to the tests stdin when doing so.
Commits on Sep 18, 2015
  1. Merge pull request #46 from seveas/more-users

    chriscool committed Sep 18, 2015
    Add some more users of sharness to README.md
Commits on Sep 17, 2015
Commits on Sep 16, 2015
  1. Merge pull request #43 from grondo/travis-update

    chriscool committed Sep 16, 2015
    travis-ci: update to container build infrastructure
Commits on Sep 6, 2015
  1. Merge pull request #33 from grondo/project-integration

    chriscool committed Sep 6, 2015
    support $SHARNESS_TEST_SRCDIR/sharness.d directory for per-project extensions
Commits on Sep 4, 2015
  1. Add test for loading sharness extensions

    grondo committed Oct 14, 2014
    Ensure loading sharness extensions from SHARNESS_TEST_SRCDIR/sharness.d
    works.
  2. Allow sharness extensions in srcdir/sharness.d

    grondo committed Oct 14, 2014
    Projects may want to extend sharness without directly modifying
    the sharness.sh test library. This patch adds support for a series
    of `extensions` to be loaded from $SHARNESS_TEST_SRCDIR/sharness.d/*.sh
    which may be used to add new functions, unset environment variables,
    extend the PATH, etc.
Commits on Sep 2, 2015
  1. Merge branch 'moy-master'

    chriscool committed Sep 2, 2015
Commits on Sep 1, 2015
  1. travis-ci: update to container build infrastructure

    grondo committed Sep 1, 2015
    Use the travis-ci.org container-based[1] build by adding
    
     sudo: false
    
    to .travis.yml config file. Since sudo is disabled, update install
    and check commands to use a path in $HOME, so that sudo is no longer
    necessary.
    
    Since container builds start quickly, there is no longer a reason to
    schedule to least-loaded language (erlang), so remove that as well.
    
    1: http://docs.travis-ci.com/user/workers/container-based-infrastructure/
  2. README.md: short summary for each command-line option

    moy committed Aug 25, 2015
    The details are still in README.git, but a short summary for each option
    should make them easier to discover for new users.
  3. actually implement the --long-tests option

    moy committed Aug 25, 2015
    The --long option was accepted by sharness.sh and documented in
    README.Git, but it was only setting $TEST_LONG which was used nowhere
    else.
    
    Mimick the behavior of Git's testsuite by setting EXPENSIVE prereq when
    $TEST_LONG is set. Git uses test_lazy_prereq which we do not have, hence
    we just set the prereq non-lazily.
Commits on Aug 25, 2015
  1. Merge pull request #42 from moy/git-multimail

    chriscool committed Aug 25, 2015
    README.md: add git-multimail in the list of (happy) users
Commits on Aug 20, 2015
  1. Merge pull request #39 from mlafeldt/talk-about-sharnessify

    mlafeldt committed Aug 20, 2015
    README: talk about Sharnessify
  2. README: talk about Sharnessify

    chriscool committed Aug 20, 2015
Commits on Jul 28, 2015
  1. Merge pull request #37 from satori/master

    chriscool committed Jul 28, 2015
    Add git-svn-fast-import to the list of projects using Sharness
Commits on Jul 27, 2015
  1. Merge pull request #30 from grondo/saved-term

    chriscool committed Jul 27, 2015
    save original TERM before sanitization
Commits on Jul 25, 2015
  1. test: add test for sub-sharness still has color

    grondo committed Jul 1, 2015
    Add a test to verify that sub-sharness tests still have color support
    when color is available from parent sharness.
  2. test: add option to run_sub_test_lib_test to run sub-test under a com…

    grondo committed Jul 1, 2015
    …mand
    
    It will be useful to run sub test-lib tests under a prefix command,
    for using test_terminal for example. Do this in the most straightforward
    and simple way possible by allowing an optional third argument to
    the run_sub_test_lib_test function.
    
    e.g.
    
      run_sub_test_lib_test name 'description' test_terminal <<-\EOF
      ...
      EOF
    
    would run the sub-test under test_terminal.
  3. test: add PERL_AND_TTY prereq in sharness.t

    grondo committed Jul 25, 2015
    Check for functionality of test-terminal.perl script and set a
    PERL_AND_TTY prereq if the script works, as a working script indicates
    we have both a working perl and way to emulate the terminal.