List for cgit developers and users
 help / color / mirror / Atom feed
From: john at keeping.me.uk (John Keeping)
Subject: [PATCH 00/12] Test improvements
Date: Mon,  8 Apr 2013 20:12:29 +0100	[thread overview]
Message-ID: <cover.1365448308.git.john@keeping.me.uk> (raw)

These are the obvious changes that integrate CGit's tests better with
the Git test framework.  There's probably some more tweaks that could be
made, but I think this covers most of the obvious things.

The couple of big patches are basically mechanical renamings, everything
else should be pretty self-explanatory I hope.

I didn't see any point changing t0010-validate-html to use test
prerequisites since we end up just adding the prerequisite to every test
there and don't need it anywhere else, and that's what skip_all is for.

John Keeping (12):
  tests: use Git test functions directly
  tests: don't let Git's test-lib create a repository
  tests: remove prepare_tests
  t0001: don't setup test repositories
  tests/.gitignore: update for using Git's test infrastructure
  tests: remove "trash" directory
  tests: put cgit onto $PATH
  .gitignore: tighten cgit ignore expression
  tests: add Valgrind support
  t0001: use test_cmp instead of 'diff -u'
  tests: use test_line_count where appropriate
  tests: use test_create_repo instead of "git init"

 .gitignore                           |   2 +-
 tests/.gitignore                     |   4 +-
 tests/setup.sh                       | 133 +++++++++++++++++++----------------
 tests/t0001-validate-git-versions.sh |  21 +++---
 tests/t0010-validate-html.sh         |  24 +++----
 tests/t0020-validate-cache.sh        |  31 ++++----
 tests/t0101-index.sh                 |  24 +++----
 tests/t0102-summary.sh               |  34 +++++----
 tests/t0103-log.sh                   |  32 ++++-----
 tests/t0104-tree.sh                  |  32 ++++-----
 tests/t0105-commit.sh                |  40 +++++------
 tests/t0106-diff.sh                  |  20 +++---
 tests/t0107-snapshot.sh              |  76 ++++++++++----------
 tests/t0108-patch.sh                 |  36 +++++-----
 tests/valgrind/bin/cgit              |  12 ++++
 15 files changed, 265 insertions(+), 256 deletions(-)
 create mode 100755 tests/valgrind/bin/cgit

-- 
1.8.2.694.ga76e9c3.dirty





             reply	other threads:[~2013-04-08 19:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 19:12 john [this message]
2013-04-08 19:12 ` [PATCH 01/12] tests: use Git test functions directly john
2013-04-08 19:12 ` [PATCH 02/12] tests: don't let Git's test-lib create a repository john
2013-04-08 19:12 ` [PATCH 03/12] tests: remove prepare_tests john
2013-04-08 19:12 ` [PATCH 04/12] t0001: don't setup test repositories john
2013-04-08 19:12 ` [PATCH 05/12] tests/.gitignore: update for using Git's test infrastructure john
2013-04-08 19:12 ` [PATCH 06/12] tests: remove "trash" directory john
2013-04-08 19:12 ` [PATCH 07/12] tests: put cgit onto $PATH john
2013-04-08 19:12 ` [PATCH 08/12] .gitignore: tighten cgit ignore expression john
2013-04-08 19:12 ` [PATCH 09/12] tests: add Valgrind support john
2013-04-08 19:23   ` Jason
2013-04-08 19:12 ` [PATCH 10/12] t0001: use test_cmp instead of 'diff -u' john
2013-04-08 19:12 ` [PATCH 11/12] tests: use test_line_count where appropriate john
2013-04-08 19:12 ` [PATCH 12/12] tests: use test_create_repo instead of "git init" john

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1365448308.git.john@keeping.me.uk \
    --to=cgit@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).