test-run
Tarantool functional testing framework (by tarantool)
tarantool-c
A new C client for Tarantool 1.6+ (by tarantool)
test-run | tarantool-c | |
---|---|---|
1 | 1 | |
14 | 26 | |
- | - | |
6.6 | 4.2 | |
about 1 month ago | about 2 months ago | |
Python | C | |
- | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
test-run
Posts with mentions or reviews of test-run.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-02-04.
-
Ten-year experience in DBMS testing
We use our own tool to run tests, test-run.py. Nowadays it may not seem reasonable to write a test runner from scratch, but it already exists, and we support it. There are different types of tests in the project — unit tests are written in C and run as binaries. Like for TAP tests, test-run.py analyzes their output in the TAP format in terms of test script success:
tarantool-c
Posts with mentions or reviews of tarantool-c.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-02-04.
-
Ten-year experience in DBMS testing
In CMake build files, we use compiler flags that enable extra checks at build time, and we run "make clean" when there are no raw warnings. Besides static analysis in the compilers, we use Coverity static analysis. We used PVS-Studio once, and it detected several non-critical errors in Tarantool itself and in tarantool-c connector. Sometimes, we used cppcheck, not that it found many bugs.
What are some alternatives?
When comparing test-run and tarantool-c you can also consider the following projects:
luatest - Tarantool test framework written in Lua
luaunit - LuaUnit is a popular unit-testing framework for Lua, with an interface typical of xUnit libraries (Python unittest, Junit, NUnit, ...). It supports several output formats (Text, TAP, JUnit, ...) to be used directly or work with Continuous Integration platforms (Jenkins, Maven, ...).
queue - Create task queues, add and take jobs, monitor failed tasks
msgpuck - A simple and efficient MsgPack binary serialization library in a self-contained header file
jepsen.tarantool - Jepsen tests for Tarantool
YCSB - Yahoo! Cloud Serving Benchmark
small - Specialized memory allocators
mejedi-tcl2lua