tursodatabase/libsql

Create new Rust test cases to increase test coverage

Open

#119 opened on Jan 26, 2023

View on GitHub
 (2 comments) (1 reaction) (0 assignees)C (16,744 stars) (490 forks)batch import
good first issuehelp wanted

Description

We already have a rudimentary set of Rust tests under https://github.com/libsql/libsql/tree/main/test/rust_suite, but that only covers the new features. Ideally, the Rust test suite should increase the test coverage of the existing set of open source tests inherited from SQLite.

Contributions very much welcome, every new test case helps!

Here's an example of a simple test case: https://github.com/libsql/libsql/blob/bd68c17adf23c038fcfc44813ea2a943b423ca63/test/rust_suite/src/lib.rs#L19-L56

Contributor guide

Tech stack
rustsql
Domain
testing
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic Rust knowledgeUnderstanding of SQLite/libSQL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90
Research direction
Examine the existing Rust test suite at test/rust suite/src/lib.rs (example line 19-56). Write similar test functions that cover more SQLite functionality. Look at the SQLite test files for inspiration on edge cases. Ensure tests compile and pass. No need to modify production code.