From: Sergey Bronnikov <sergeyb@tarantool.org>
To: tarantool-patches@dev.tarantool.org, v.shpilevoy@tarantool.org
Subject: [Tarantool-patches] [PATCH v2 4/3][msgpuck] test: make test output TAP-compliant
Date: Mon, 8 Jun 2020 19:03:18 +0300 [thread overview]
Message-ID: <4aaea4c0d0bab5b4272d14286ecab6a2a7561040.1591632019.git.sergeyb@tarantool.org> (raw)
In-Reply-To: <cover.1591631501.git.sergeyb@tarantool.org>
Part of: https://github.com/tarantool/tarantool/issues/5000
---
test/test.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/test/test.c b/test/test.c
index 42b79eb..5e2430e 100644
--- a/test/test.c
+++ b/test/test.c
@@ -57,6 +57,9 @@ plan(int count)
tests_done[level] = 0;
tests_failed[level] = 0;
+ if (level == 0)
+ printf("TAP version 13\n");
+
__space(stdout);
printf("%d..%d\n", 1, plan_test[level]);
}
--
2.23.0
--
sergeyb@
next prev parent reply other threads:[~2020-06-08 16:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 15:58 [Tarantool-patches] [PATCH v2 0/3] Make unit tests TAP-compliant sergeyb
2020-06-08 15:58 ` [Tarantool-patches] [PATCH v2 1/3] test: update unit test lib to produce TAP-compliant output sergeyb
2020-06-08 23:55 ` Vladislav Shpilevoy
2020-06-09 18:25 ` Sergey Bronnikov
2020-06-08 15:58 ` [Tarantool-patches] [PATCH v2 2/3] test: update unit tests to make them TAP-compliant sergeyb
2020-06-08 23:55 ` Vladislav Shpilevoy
2020-06-09 16:04 ` Sergey Bronnikov
2020-06-11 18:42 ` Vladislav Shpilevoy
2020-06-08 15:58 ` [Tarantool-patches] [PATCH v2 3/3] msgpuck: bump version to make test output TAP-compliant sergeyb
2020-06-08 16:03 ` Sergey Bronnikov [this message]
2020-06-11 18:42 ` [Tarantool-patches] [PATCH v2 4/3] test: add additional checks Vladislav Shpilevoy
2020-06-11 18:42 ` [Tarantool-patches] [PATCH v2 0/3] Make unit tests TAP-compliant Vladislav Shpilevoy
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=4aaea4c0d0bab5b4272d14286ecab6a2a7561040.1591632019.git.sergeyb@tarantool.org \
--to=sergeyb@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v2 4/3][msgpuck] test: make test output TAP-compliant' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox