From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
Subject: ab/lib-subtest
Date: Fri, 01 Oct 2021 17:05:55 +0200 [thread overview]
Message-ID: <875yugrdfw.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqh7e18soj.fsf@gitster.g>
On Thu, Sep 30 2021, Junio C Hamano wrote:
> * ab/lib-subtest (2021-09-22) 9 commits
> - test-lib tests: get rid of copy/pasted mock test code
> - test-lib tests: assert 1 exit code, not non-zero
> - test-lib tests: refactor common part of check_sub_test_lib_test*()
> - test-lib tests: avoid subshell for "test_cmp" for readability
> - test-lib tests: don't provide a description for the sub-tests
> - test-lib tests: split up "write and run" into two functions
> - test-lib tests: move "run_sub_test" to a new lib-subtest.sh
> - Merge branch 'ps/t0000-output-directory-fix' into ab/lib-subtest
> - Merge branch 'jk/t0000-subtests-fix' into ab/lib-subtest
>
> Updates to the tests in t0000 to test the test framework.
>
> Will merge to 'next'?
I think it's ready, Carlo (CC'd) gave it a look and I re-rolled
addressing his feedback:
https://lore.kernel.org/git/cover-v4-0.7-00000000000-20210922T111734Z-avarab@gmail.com/
It's something I have some test-lib.sh UX improvements/simplification
waiting on, so having it go forward would be great :) Thanks!
next prev parent reply other threads:[~2021-10-01 15:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 1:01 What's cooking in git.git (Sep 2021, #09; Thu, 30) Junio C Hamano
2021-10-01 6:20 ` en/removing-untracked-fixes [Was: Re: What's cooking in git.git (Sep 2021, #09; Thu, 30)] Elijah Newren
2021-10-01 8:51 ` Ævar Arnfjörð Bjarmason
2021-10-01 17:05 ` en/removing-untracked-fixes [ Junio C Hamano
2021-10-01 6:31 ` en/remerge-diff [Was: Re: What's cooking in git.git (Sep 2021, #09; Thu, 30)] Elijah Newren
2021-10-01 7:01 ` Jeff King
2021-10-01 12:05 ` What's cooking in git.git (Sep 2021, #09; Thu, 30) Ævar Arnfjörð Bjarmason
2021-10-01 12:08 ` ab/fsck-unexpected-type Ævar Arnfjörð Bjarmason
2021-10-01 14:32 ` ab/parse-options-cleanup Ævar Arnfjörð Bjarmason
2021-10-01 14:35 ` ab/sanitize-leak-ci & more leak fixes soon-or-not Ævar Arnfjörð Bjarmason
2021-10-01 14:48 ` ab/refs-errno-cleanup Ævar Arnfjörð Bjarmason
2021-10-01 14:56 ` What's cooking in git.git (Sep 2021, #09; Thu, 30) Jeff Hostetler
2021-10-01 15:01 ` ab/align-parse-options-help & ab/help-config-vars Ævar Arnfjörð Bjarmason
2021-10-01 15:05 ` Ævar Arnfjörð Bjarmason [this message]
2021-10-01 15:07 ` ab/config-based-hooks-1 Ævar Arnfjörð Bjarmason
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=875yugrdfw.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=carenas@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.