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.
13 lines
575 B
C
13 lines
575 B
C
#ifndef TESTS_TEST_PLUGINS_DISCO_H
|
|
#define TESTS_TEST_PLUGINS_DISCO_H
|
|
|
|
void disco_get_features__returns__empty_list_when_none(void** state);
|
|
void disco_add_feature__updates__added_feature(void** state);
|
|
void disco_close__updates__resets_features(void** state);
|
|
void disco_get_features__returns__all_added_features(void** state);
|
|
void disco_add_feature__updates__not_duplicate_feature(void** state);
|
|
void disco_remove_features__updates__removes_plugin_features(void** state);
|
|
void disco_remove_features__updates__not_remove_when_more_than_one_reference(void** state);
|
|
|
|
#endif
|