# Ability to give tests custom names

**URL:** <https://internals.rust-lang.org/t/ability-to-give-tests-custom-names/21286>\
**Category:** Uncategorized\
**Created:** [July 31, 2024, 9:33am UTC](https://internals.rust-lang.org/t/ability-to-give-tests-custom-names/21286 "2024-07-31T09:33:30Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**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:** [August 1, 2024, 2:29pm UTC](https://internals.rust-lang.org/t/ability-to-give-tests-custom-names/21286/2 "2024-08-01T14:29:58Z")

</div>

From [Skippable Tests - #5 by epage](https://internals.rust-lang.org/t/skippable-tests/21260/5)

> [@Skippable Tests](https://internals.rust-lang.org/t/skippable-tests/21260/5):
>
> 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/)

For me, what I'm hopeful for your case is to develop a custom test harness that supports data-driven tests that would call out the path to the data (and maybe when we report the relevant file/line of a test in json, we point back to the data). Unsure if this would fully work with your case or if code-gen is a hard requirement. Even if it is, I think this kind of scheme would work.

---

_[View the full topic](https://internals.rust-lang.org/t/ability-to-give-tests-custom-names/21286)._