From: "Philip Peterson via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Philip Peterson <philip.c.peterson@gmail.com>,
Philip Peterson <philip.c.peterson@gmail.com>
Subject: [PATCH 2/2] apply: rewrite unit tests with structured cases
Date: Mon, 19 Feb 2024 04:45:38 +0000 [thread overview]
Message-ID: <7dab12ab7b8af3e6a0778fc1a01dd1479990bcff.1708317938.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1677.git.git.1708317938.gitgitgadget@gmail.com>
From: Philip Peterson <philip.c.peterson@gmail.com>
The imperative format was a little hard to read, so I rewrote the test cases
in a declarative style by defining a common structure for each test case and
its assertions.
Signed-off-by: Philip Peterson <philip.c.peterson@gmail.com>
---
t/unit-tests/t-apply.c | 123 ++++++++++++++++++++++++++---------------
1 file changed, 78 insertions(+), 45 deletions(-)
diff --git a/t/unit-tests/t-apply.c b/t/unit-tests/t-apply.c
index ff0abfb2e0b..2b78624b690 100644
--- a/t/unit-tests/t-apply.c
+++ b/t/unit-tests/t-apply.c
@@ -3,65 +3,98 @@
#define FAILURE -1
-static void setup_static(const char *line, int len, int offset,
- const char *expect, int assert_result,
- unsigned long assert_p1,
- unsigned long assert_p2)
+typedef struct test_case {
+ const char *line;
+ const char *expect_suffix;
+ int offset;
+ unsigned long expect_p1;
+ unsigned long expect_p2;
+ int expect_result;
+} test_case;
+
+static void setup_static(struct test_case t)
{
unsigned long p1 = 9999;
unsigned long p2 = 9999;
- int result = parse_fragment_range(line, len, offset, expect, &p1, &p2);
- check_int(result, ==, assert_result);
- check_int(p1, ==, assert_p1);
- check_int(p2, ==, assert_p2);
+ int result = parse_fragment_range(t.line, strlen(t.line), t.offset, t.expect_suffix, &p1, &p2);
+ check_int(result, ==, t.expect_result);
+ check_int(p1, ==, t.expect_p1);
+ check_int(p2, ==, t.expect_p2);
}
int cmd_main(int argc, const char **argv)
{
- char* text;
- int expected_result;
-
- /* Success */
- text = "@@ -4,4 +";
- expected_result = 9;
- TEST(setup_static(text, strlen(text), 4, " +", expected_result, 4, 4),
- "well-formed range");
+ TEST(setup_static((struct test_case) {
+ .line = "@@ -4,4 +",
+ .offset = 4,
+ .expect_suffix = " +",
+ .expect_result = 9,
+ .expect_p1 = 4,
+ .expect_p2 = 4
+ }), "well-formed range");
- text = "@@ -4 +8 @@";
- expected_result = 7;
- TEST(setup_static(text, strlen(text), 4, " +", expected_result, 4, 1),
- "non-comma range");
+ TEST(setup_static((struct test_case) {
+ .line = "@@ -4 +8 @@",
+ .offset = 4,
+ .expect_suffix = " +",
+ .expect_result = 7,
+ .expect_p1 = 4,
+ .expect_p2 = 1
+ }), "non-comma range");
- /* Failure */
- text = "@@ -X,4 +";
- expected_result = FAILURE;
- TEST(setup_static(text, strlen(text), 4, " +", expected_result, 9999, 9999),
- "non-digit range (first coordinate)");
+ TEST(setup_static((struct test_case) {
+ .line = "@@ -X,4 +",
+ .offset = 4,
+ .expect_suffix = " +",
+ .expect_result = FAILURE,
+ .expect_p1 = 9999,
+ .expect_p2 = 9999
+ }), "non-digit range (first coordinate)");
- text = "@@ -4,X +";
- expected_result = FAILURE;
- TEST(setup_static(text, strlen(text), 4, " +", expected_result, 4, 1), // p2 is 1, a little strange but not catastrophic
- "non-digit range (second coordinate)");
+ TEST(setup_static((struct test_case) {
+ .line = "@@ -4,X +",
+ .offset = 4,
+ .expect_suffix = " +",
+ .expect_result = FAILURE,
+ .expect_p1 = 4,
+ .expect_p2 = 1 // A little strange this is 1, but not end of the world
+ }), "non-digit range (second coordinate)");
- text = "@@ -4,4 -";
- expected_result = FAILURE;
- TEST(setup_static(text, strlen(text), 4, " +", expected_result, 4, 4),
- "non-expected trailing text");
+ TEST(setup_static((struct test_case) {
+ .line = "@@ -4,4 -",
+ .offset = 4,
+ .expect_suffix = " +",
+ .expect_result = FAILURE,
+ .expect_p1 = 4,
+ .expect_p2 = 4
+ }), "non-expected trailing text");
- text = "@@ -4,4";
- expected_result = FAILURE;
- TEST(setup_static(text, strlen(text), 4, " +", expected_result, 4, 4),
- "not long enough for expected trailing text");
+ TEST(setup_static((struct test_case) {
+ .line = "@@ -4,4",
+ .offset = 4,
+ .expect_suffix = " +",
+ .expect_result = FAILURE,
+ .expect_p1 = 4,
+ .expect_p2 = 4
+ }), "not long enough for expected trailing text");
- text = "@@ -4,4";
- expected_result = FAILURE;
- TEST(setup_static(text, strlen(text), 7, " +", expected_result, 9999, 9999),
- "not long enough for offset");
+ TEST(setup_static((struct test_case) {
+ .line = "@@ -4,4",
+ .offset = 7,
+ .expect_suffix = " +",
+ .expect_result = FAILURE,
+ .expect_p1 = 9999,
+ .expect_p2 = 9999
+ }), "not long enough for offset");
- text = "@@ -4,4";
- expected_result = FAILURE;
- TEST(setup_static(text, strlen(text), -1, " +", expected_result, 9999, 9999),
- "negative offset");
+ TEST(setup_static((struct test_case) {
+ .line = "@@ -4,4",
+ .offset = -1,
+ .expect_suffix = " +",
+ .expect_result = FAILURE,
+ .expect_p1 = 9999,
+ .expect_p2 = 9999
+ }), "negative offset");
return test_done();
}
--
gitgitgadget
next prev parent reply other threads:[~2024-02-19 4:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 4:45 [PATCH 0/2] apply: add unit tests for parse_range Philip Peterson via GitGitGadget
2024-02-19 4:45 ` [PATCH 1/2] apply: add unit tests for parse_range and rename to parse_fragment_range Philip Peterson via GitGitGadget
2024-02-19 21:35 ` Junio C Hamano
2024-04-04 3:53 ` Philip
2024-04-04 19:27 ` Junio C Hamano
2024-02-19 4:45 ` Philip Peterson via GitGitGadget [this message]
2024-02-19 21:49 ` [PATCH 2/2] apply: rewrite unit tests with structured cases Junio C Hamano
2024-02-19 22:04 ` Kristoffer Haugsbakk
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7dab12ab7b8af3e6a0778fc1a01dd1479990bcff.1708317938.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=philip.c.peterson@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).