Repository navigation
Conversation
Contributors had no in-tree instructions for the tap tests under t/. Describe the cmake/ctest workflow used in CI and how to run a single test with LUA_PATH and ENGINE. Closes tarantool#101
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Document how to run the tap tests under
t/using the samecmake/make checkflow as CI, and how to run an individual test withLUA_PATHandENGINE.Motivation
New contributors had no in-tree instructions for running the test suite (#101).
How tested
cmake . && make checkfrom a source checkout (local Tarantool 2.6.0: 60/62 pass; the two*-240-ro-on-disconnect.tfailures look tied to that older Tarantool version, not this docs change)LUA_PATH="$PWD/?.lua;$PWD/?/init.lua;" ENGINE=memtx tarantool t/000-init.tCloses #101