From: "Karl Hasselström" <kha@treskal.com>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org
Subject: [StGit PATCH 0/2] Test improvements
Date: Tue, 08 Jul 2008 06:03:04 +0200 [thread overview]
Message-ID: <20080708035750.23134.75833.stgit@yoghurt> (raw)
First, a change across all the tests to make sure that stg always
exits with the correct exit code even when it's not zero. This lets us
detect the difference between a controlled failure and a crash.
Second, a rather comprehensive test fir "stg edit" -- we didn't test
it at all. Which can be seen in the number of failures in this test.
They are available in kha/safe. The patches in kha/experimental have
been rebased on top of these, resulting in a number of new test
failures that I've had to fix.
---
Karl Hasselström (2):
Test for "stg edit"
Test for specific exit code
t/README | 6 +
t/t0001-subdir-branches.sh | 12 +--
t/t0002-status.sh | 2
t/t1000-branch-create.sh | 8 +-
t/t1001-branch-rename.sh | 2
t/t1002-branch-clone.sh | 2
t/t1200-push-modified.sh | 2
t/t1202-push-undo.sh | 4 -
t/t1203-push-conflict.sh | 4 -
t/t1205-push-subdir.sh | 4 -
t/t1301-repair.sh | 2
t/t1302-repair-interop.sh | 4 -
t/t1400-patch-history.sh | 2
t/t1501-sink.sh | 2
t/t1600-delete-one.sh | 4 -
t/t1601-delete-many.sh | 2
t/t2000-sync.sh | 4 -
t/t2101-pull-policy-pull.sh | 2
t/t2200-rebase.sh | 2
t/t2500-clean.sh | 2
t/t2900-rename.sh | 8 +-
t/t3000-dirty-merge.sh | 2
t/t3300-edit.sh | 205 +++++++++++++++++++++++++++++++++++++++++++
t/t4000-upgrade.sh | 2
t/test-lib.sh | 24 +++++
25 files changed, 271 insertions(+), 42 deletions(-)
create mode 100755 t/t3300-edit.sh
--
Karl Hasselström, kha@treskal.com
www.treskal.com/kalle
next reply other threads:[~2008-07-08 4:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 4:03 Karl Hasselström [this message]
2008-07-08 4:03 ` [StGit PATCH 1/2] Test for specific exit code Karl Hasselström
2008-07-08 4:03 ` [StGit PATCH 2/2] Test for "stg edit" Karl Hasselström
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=20080708035750.23134.75833.stgit@yoghurt \
--to=kha@treskal.com \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
/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).