Split the unit-tests from the source code · meilisearch/MeiliSearch#5116

(2 留言) (2 反應) (0 負責人)Rust (20,887 star) (733 fork)batch import

good first issuemaintenance

描述

Currently, there is a lot of files containing a lot of codes, and then literally thousands of lines of tests at the end of the tests. That's becoming an issue because it slows down rust analyzer and makes development harder.

We should look at the biggest files in the repository. If they contain many tests at the end, create a new file with the same name postfixed by _tests and import it in the lib.rs/mod.rs. So for example if we have this structure:

src
├── index.rs
└── lib.rs

And the index.rs contains a lot of tests, then you should update the structure like that and move the tests to index_tests.rs:

src
├── index.rs
├── index_tests.rs
└── lib.rs

[!IMPORTANT] Please open PR per files to ease the reviewer work

貢獻者指南

技術棧: rust
領域: testingdeveloper experience
議題類型: refactor
難度: 2
預計時間: half day
活動狀態: fresh
清晰度: clear
前置要求: Basic Rust knowledgeFamiliarity with Meilisearch codebaseUnderstanding of Rust module system
新手友善度: 85
研究方向: Identify the largest source files in the `src` directory that contain many `#[cfg(test)]` modules or inline tests at the end. For each such file (e.g., `index.rs`), create a new file `index tests.rs` in the same directory, move all test related code to it, and add `mod index tests;` in the corresponding `lib.rs` or `mod.rs`. Ensure that all tests still pass after the split. Start with one file per pull request as instructed. See the issue for an example.