tests: standardize naming convention

Use a behavior-driven naming convention for unit tests.

Functions are now named using the pattern: [unit]__[verb]__[scenario]
The __ works as a semantic separator.

Examples:
* jid_create__returns__null_from_null()
* cmd_connect__shows__usage_when_no_server_value

Benefits:
* Easy to find all tests associated with a specific function using the
  mandatory prefix.
* Test output in CI now explicitly describes the unit, the expected
  outcome, and the scenario being tested.

Also disabled keyhandlers tests due to missing code in src/ui.
This commit is contained in:
Michael Vetter
2026-02-28 12:41:33 +01:00
parent a7408a970e
commit e81435be06
53 changed files with 1601 additions and 1433 deletions

View File

@@ -13,7 +13,7 @@
#define CMD_SUB "/sub"
void
cmd_sub_shows_message_when_not_connected(void** state)
cmd_sub__shows__message_when_not_connected(void** state)
{
gchar* args[] = { NULL };
@@ -26,7 +26,7 @@ cmd_sub_shows_message_when_not_connected(void** state)
}
void
cmd_sub_shows_usage_when_no_arg(void** state)
cmd_sub__shows__usage_when_no_arg(void** state)
{
gchar* args[] = { NULL };