Tarantool development patches archive
 help / color / mirror / Atom feed
From: "Alexander V. Tikhonov" <avtikhon@tarantool.org>
To: Oleg Piskunov <o.piskunov@tarantool.org>,
	Igor Munkin <imun@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: [Tarantool-patches] [PATCH v2 0/2] test: rename test files and cleanup it
Date: Thu, 27 Feb 2020 16:52:08 +0300	[thread overview]
Message-ID: <cover.1582810913.git.avtikhon@tarantool.org> (raw)

test: rename test files and cleanup it

Cleaned up the tests code:
- added local definitions for the variables
- added os.exit() routine at the tests finish
- changed added information messages to test:ok() calls

Renamed test files in the following way:
<repo>-<number>-<comment>.test.lua
where "external repo" is github repository:
  gh - tarantool/tarantool
  lj - luajit/luajit
  or - openresty/lua-resty-core

Close #4655

Changed V2:
- renamed tests as suggested
- added tap.test names

0/2 https://lists.tarantool.org/pipermail/tarantool-patches/2019-December/013087.html
1/2 https://lists.tarantool.org/pipermail/tarantool-patches/2019-December/013086.html
2/2 https://lists.tarantool.org/pipermail/tarantool-patches/2019-December/013085.html

Github: https://github.com/tarantool/LuaJIT/tree/avtikhon/gh-4655-cleanup-tests
Issue: https://github.com/tarantool/tarantool/issues/4655

Alexander V. Tikhonov (2):
  test: cleanup tests code
  test: rename test files

 ... gh-3196-incorrect-string-length.test.lua} |  8 +++----
 ...h-4476-fix-string-find-recording.test.lua} |  6 ++---
 ...st.lua => gh-4560-pairsmm-is-set.test.lua} |  8 ++++---
 ...lj-494-table-chain-infinite-loop.test.lua} | 23 ++++++++++---------
 ...=> lj-505-fold-icorrect-behavior.test.lua} |  7 +++---
 ...est.lua => or-232-unsink-64-kptr.test.lua} |  7 +++---
 ...=> or-524-fold-icorrect-behavior.test.lua} |  4 ++--
 7 files changed, 34 insertions(+), 29 deletions(-)
 rename test/{gh.test.lua => gh-3196-incorrect-string-length.test.lua} (56%)
 rename test/{fix_string_find_recording.test.lua => gh-4476-fix-string-find-recording.test.lua} (95%)
 rename test/{pairsmm_tarantool_4560.test.lua => gh-4560-pairsmm-is-set.test.lua} (89%)
 rename test/{table_chain_bug_LuaJIT_494.test.lua => lj-494-table-chain-infinite-loop.test.lua} (89%)
 rename test/{fold_bug_LuaJIT_505.test.lua => lj-505-fold-icorrect-behavior.test.lua} (72%)
 rename test/{unsink_64_kptr.test.lua => or-232-unsink-64-kptr.test.lua} (87%)
 rename test/{fold_bug_LuaJIT_524.test.lua => or-524-fold-icorrect-behavior.test.lua} (85%)

-- 
2.17.1

             reply	other threads:[~2020-02-27 13:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27 13:52 Alexander V. Tikhonov [this message]
2020-02-27 13:52 ` [Tarantool-patches] [PATCH v2 1/2] test: cleanup tests code Alexander V. Tikhonov
2020-02-28 18:36   ` Igor Munkin
2020-03-20 12:31     ` Alexander Tikhonov
2020-02-27 13:52 ` [Tarantool-patches] [PATCH v2 2/2] test: rename test files Alexander V. Tikhonov
2020-02-28 18:37   ` Igor Munkin
2020-02-28 18:57     ` Igor Munkin
2020-03-20 12:39     ` Alexander Tikhonov

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=cover.1582810913.git.avtikhon@tarantool.org \
    --to=avtikhon@tarantool.org \
    --cc=imun@tarantool.org \
    --cc=o.piskunov@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v2 0/2] test: rename test files and cleanup it' \
    /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