This document discusses test case naming conventions and strategies. It argues that test cases should be named after the product they test rather than the requirements or project, since those may change over time. The naming should follow a hierarchy that indicates the element being tested, such as the menu, group, icon, and option. This provides context and helps identify what is being tested. Well-named test cases can guide understanding of the system without needing additional documentation. The document provides examples of test case names for Microsoft PowerPoint and Google applications that follow this recommended hierarchical convention.