# Test naming convention

DevFeed: [Test naming convention](<https://devfeed.tech/articles/test-naming-convention-27302.md>)

Original publisher: [Read original article](<https://blog.pchudzik.com/201903/test-names-conventions/>)

Published: 2019-03-14T00:00:00Z

Content type: tutorial

Language: en

Sources: [Paweł Chudzik](<https://devfeed.tech/sources/pawe-chudzik.md>)

Topics: [Automation](<https://devfeed.tech/topics/automation.md>), [unit tests](<https://devfeed.tech/topics/unit-tests.md>), [Development](<https://devfeed.tech/topics/development.md>), [Code review](<https://devfeed.tech/topics/code-review.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [automated](<https://devfeed.tech/tags/automated.md>), [automation](<https://devfeed.tech/tags/automation.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [database](<https://devfeed.tech/tags/database.md>), [excel](<https://devfeed.tech/tags/excel.md>), [ide](<https://devfeed.tech/tags/ide.md>), [integration-test](<https://devfeed.tech/tags/integration-test.md>), [tests](<https://devfeed.tech/tags/tests.md>), [verify](<https://devfeed.tech/tags/verify.md>)

## AI overview

This tutorial explains how to use automated tests to enforce naming conventions for test groups. It distinguishes fast unit tests from integration tests involving I/O, databases, external APIs, reports, and Excel imports, and argues that convention checks can serve as both automated enforcement and living documentation.

## Source excerpt

How to introduce automated checks that will guarantee that conventions are followed in an example of test naming convention. I'm going to focus on creating automated process that will verify if test names do match conventions. Automation will allow us to forget about the rule because the computer will ensure it's followed. Test that I'm going to introduce will be living documentation inside the project and ensure no one will miss nor forget about the way we group tests. Read more