From 3dd6a8a1545bb0c68e074c20e3c21c3dfb87a5c2 Mon Sep 17 00:00:00 2001 From: "sheng.haiyang" Date: Tue, 12 Sep 2017 17:52:48 +0800 Subject: [PATCH 1/2] update tck README --- CopyrightWaivers.txt | 1 + tck/README.md | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/CopyrightWaivers.txt b/CopyrightWaivers.txt index 596260dc..7ef479f1 100644 --- a/CopyrightWaivers.txt +++ b/CopyrightWaivers.txt @@ -39,3 +39,4 @@ akarnokd | David Karnok, akarnokd@gmail.com egetman | Evgeniy Getman, getman.eugene@gmail.com patriknw | Patrik Nordwall, patrik.nordwall@gmail.com, Lightbend Inc angelsanz | Ángel Sanz, angelsanz@users.noreply.github.com +shenghaiyang | 盛海洋, shenghaiyang@aliyun.com diff --git a/tck/README.md b/tck/README.md index 6baa655f..6fe670c2 100644 --- a/tck/README.md +++ b/tck/README.md @@ -41,7 +41,7 @@ Since the TCK is aimed at Reactive Stream implementers, looking into the sources In order to make mapping between test cases and Specification rules easier, each test case covering a specific Specification rule abides the following naming convention: `TYPE_spec###_DESC` where: -* `TYPE` is one of: [#type-required](required), [#type-optional](optional), [#type-stochastic](stochastic) or [#type-untested](untested) which describe if this test is covering a Rule that MUST or SHOULD be implemented. The specific words are explained in detail below. +* `TYPE` is one of: [required](#type-required), [optional](#type-optional), [stochastic](#type-stochastic) or [untested](#type-untested) which describe if this test is covering a Rule that MUST or SHOULD be implemented. The specific words are explained in detail below. * `###` is the Rule number (`1.xx` Rules are about `Publisher`s, `2.xx` Rules are about Subscribers etc.) * `DESC` is a short explanation of what exactly is being tested in this test case, as sometimes one Rule may have multiple test cases in order to cover the entire Rule. From 035cb0a8fa03b249e5a2b5471903b20d4083a7a2 Mon Sep 17 00:00:00 2001 From: shenghaiyang Date: Thu, 16 Nov 2017 10:15:51 +0800 Subject: [PATCH 2/2] Update tck-flow README.md --- tck-flow/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tck-flow/README.md b/tck-flow/README.md index 03a93a88..6c2ac9fb 100644 --- a/tck-flow/README.md +++ b/tck-flow/README.md @@ -41,7 +41,7 @@ Since the TCK is aimed at Reactive Stream implementers, looking into the sources In order to make mapping between test cases and Specification rules easier, each test case covering a specific Specification rule abides the following naming convention: `TYPE_spec###_DESC` where: -* `TYPE` is one of: [#type-required](required), [#type-optional](optional), [#type-stochastic](stochastic) or [#type-untested](untested) which describe if this test is covering a Rule that MUST or SHOULD be implemented. The specific words are explained in detail below. +* `TYPE` is one of: [required](#type-required), [optional](#type-optional), [stochastic](#type-stochastic) or [untested](#type-untested) which describe if this test is covering a Rule that MUST or SHOULD be implemented. The specific words are explained in detail below. * `###` is the Rule number (`1.xx` Rules are about `Publisher`s, `2.xx` Rules are about Subscribers etc.) * `DESC` is a short explanation of what exactly is being tested in this test case, as sometimes one Rule may have multiple test cases in order to cover the entire Rule.