e81435be06
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.
11 lines
478 B
C
11 lines
478 B
C
#ifndef TESTS_TEST_SERVER_EVENTS_H
|
|
#define TESTS_TEST_SERVER_EVENTS_H
|
|
|
|
void sv_ev_contact_online__shows__presence_in_console_when_set_online(void** state);
|
|
void sv_ev_contact_online__shows__presence_in_console_when_set_all(void** state);
|
|
void sv_ev_contact_online__shows__dnd_presence_in_console_when_set_all(void** state);
|
|
void sv_ev_contact_offline__updates__removes_chat_session(void** state);
|
|
void sv_ev_lost_connection__updates__clears_chat_sessions(void** state);
|
|
|
|
#endif
|