# Skippable Tests **URL:** \ **Category:** language design\ **Created:** [July 26, 2024, 11:39pm UTC](https://internals.rust-lang.org/t/skippable-tests/21260 "2024-07-26T23:39:33Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![epage](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/epage/32/3171_2.png) [@epage](https://internals.rust-lang.org/u/epage)\ **Post date:** [July 29, 2024, 3:59pm UTC](https://internals.rust-lang.org/t/skippable-tests/21260/5 "2024-07-29T15:59:34Z")
The rough plan (informal agreement with libs-api over a year ago, no conversations in testing-devex yet) is to freeze libtest roughly as it is, maybe removing functionality where possible (unstable features, features without strict compatibility, etc) and instead put the focus on custom test harnesses. I documented my thoughts and the libs-api discussion [on my blog](https://epage.github.io/blog/2023/06/iterating-on-test/) and the various efforts are being tracked in the [testing-devex repo](https://github.com/rust-lang/testing-devex-team/issues/) --- _[View the full topic](https://internals.rust-lang.org/t/skippable-tests/21260)._