From 73488abb45dc003bc26d49188812f481244bec60 Mon Sep 17 00:00:00 2001 From: Shingo OKAWA Date: Sat, 27 Sep 2025 16:07:07 +0900 Subject: [PATCH] docs(contributing): fix link to `widgets_block_renders` test (#2101) The `CONTRIBUTING.md` referenced `tests/widgets_block.rs`, but the correct path is `ratatui/tests/widgets_block.rs`. Updated the link so that readers can navigate to the test example without 404 error. --------- Signed-off-by: Shingo OKAWA --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 7b4638a3..05bf88cb 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -181,7 +181,7 @@ good, but this can always be improved. Focus on keeping the tests simple and obv tests for all new or modified code. Beside the usual doc and unit tests, one of the most valuable test you can write for Ratatui is a test against the `TestBackend`. It allows you to assert the content of the output buffer that would have been flushed to the terminal after a given draw call. -See `widgets_block_renders` in [tests/widgets_block.rs](./tests/widget_block.rs) for an example. +See `widgets_block_renders` in [ratatui/tests/widgets_block.rs](./ratatui/tests/widgets_block.rs) for an example. When writing tests, generally prefer to write unit tests and doc tests directly in the code file being tested rather than integration tests in the `tests/` folder.