# TiKV Authors - Fail - Rust (Highlights) ![rw-book-cover|256](https://readwise-assets.s3.amazonaws.com/static/images/article0.00998d930354.png) ## Metadata **Cover**:: https://readwise-assets.s3.amazonaws.com/static/images/article0.00998d930354.png **Source**:: #from/readwise **Zettel**:: #zettel/fleeting **Status**:: #x **Authors**:: [[TiKV Authors]] **Full Title**:: Fail - Rust **Category**:: #articles #readwise/articles **Category Icon**:: 📰 **URL**:: [docs.rs](https://docs.rs/fail/0.4.0/fail/index.html) **Host**:: [[docs.rs]] **Highlighted**:: [[2021-08-31]] **Created**:: [[2022-09-26]] ## Highlights - Even if a test does not itself turn on any fail points, code that it runs could trigger a fail point that was configured by another thread. Because of this it is a best practice to put all fail point unit tests into their own binary.