cmocka | This is a mirror of the cmocka unit testing framework https

by gkdr C Version: Current License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(7)Vulnerabilities Install Support

kandi X-RAY | cmocka Summary

cmocka is a C library. cmocka has no bugs, it has no vulnerabilities and it has low support. However cmocka has a Non-SPDX License. You can download it from GitLab.

cmocka is an elegant unit testing framework for C with support for mock objects. It only requires the standard C library, works on a range of computing platforms (including embedded) and with different compilers. For information about how to use the cmocka unit testing framework see doc/index.html or

Support

Quality

Security

License

Reuse

Support

cmocka has a low active ecosystem.

It has 0 star(s) with 0 fork(s). There are no watchers for this library.

It had no major release in the last 6 months.

cmocka has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of cmocka is current.

Quality

cmocka has no bugs reported.

Security

cmocka has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

cmocka has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

cmocka releases are not available. You will need to build from source code and install.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of cmocka

Get all kandi verified functions for this library.

cmocka Key Features

No Key Features are available at this moment for cmocka.

cmocka Examples and Code Snippets

No Code Snippets are available at this moment for cmocka.

Community Discussions

Trending Discussions on cmocka

Cmocka - should we all be creating one executable per test for isolating static variables?

Wrapped function pointer parameter changes if return value struct has too many members

set_target_properties does not work with multiple --wrap functions

Mocking functions with cmocka

libssh's functions couldn't be found on qt and cmake error while building libssh

Understanding writing a CMakeLists.txt

Cmocka unit testing with C: mocking nested function calls

QUESTION

Cmocka - should we all be creating one executable per test for isolating static variables?

Asked 2022-Feb-15 at 08:02

Failure

Given the following cmocka test with a static variable in a dependency:

main.c

...

ANSWER

Answered 2022-Feb-15 at 08:02

Yes, if you have a static variable in the tested object, you need to compile separated tests if they expect a "fresh" test object.

I would do this anyway, each test in a separated executable, since you have a Singleton in your test object.

This is a fine example why the Singleton pattern is an anti-pattern today. It is hard to test.

Source https://stackoverflow.com/questions/71118831

QUESTION

Wrapped function pointer parameter changes if return value struct has too many members

Asked 2022-Feb-14 at 17:00

I compile the following main.c with gcc main.c -Wl,--wrap=foo -lcmocka:

...

ANSWER

Answered 2022-Feb-14 at 17:00

You need to add the declaration for the foo function. Currently foo(1, 1, 1, bar); will use an implicit declaration of int foo(). Implicit declarations are invalid since C99 so you should be able to turn on more warnings to catch this (-Wimplicit-function-declaration -Werror).

The implicitly declared function takes the arguments you've given it (which will actually match __wrap_foo, given that int32_t is a typedef for int) and will return int, not ExampleStruct, so your program will have Undefined Behavior.

Example:

Source https://stackoverflow.com/questions/71087449

QUESTION

set_target_properties does not work with multiple --wrap functions

Asked 2021-Nov-20 at 11:54

#include 
#include 
#include 
#include 
#include "stdint.h"

typedef enum {
    eSTATE_STARTUP,
    eSTATE_ADDRESSING,
    eSTATE_RANDOMISE,
    eSTATE_SELECTED
}e_State_t;

void test_main()
{
    static e_State_t e_state = eSTATE_STARTUP;

    if(get_rx_dali_flag())
      {
          application_process(&e_state);
      }

      switch(e_state)
      {
          case eSTATE_STARTUP:
          {
              set_led_frequency(0);
              break;
          }
          case eSTATE_ADDRESSING:
          {
              set_led_frequency(1);
              break;
          }
          case eSTATE_RANDOMISE:
          {
              set_led_frequency(10);
              break;
          }
          case eSTATE_SELECTED:
          {
              set_led_frequency(100);
              break;
          }
          default:
              break;
      }
}



int __wrap_get_rx_dali_flag(void)
{
    int data_available = mock_type(uint8_t);
    return data_available;
}

void __wrap_application_process(e_State_t * ptr_state)
{   
    check_expected_ptr(ptr_state);
    *ptr_state = mock_type(e_State_t);
}

void __wrap_set_led_frequency(uint16_t frequency)
{
    assert_int_equal(frequency, 1);
}



void main_should_setLedFreq_1_when_stateADDRESSING()
{
    will_return(__wrap_get_rx_dali_flag, 1);
    will_return(__wrap_application_process, eSTATE_ADDRESSING);

    test_main();
}



int main()
{
    const struct CMUnitTest tests[] =
    {
        cmocka_unit_test(main_should_setLedFreq_1_when_stateADDRESSING),
    };

    return cmocka_run_group_tests(tests, NULL, NULL);
}

...

ANSWER

Answered 2021-Nov-20 at 11:54

Just use:

Source https://stackoverflow.com/questions/70045411

QUESTION

Mocking functions with cmocka

Asked 2021-Jul-02 at 10:59

I'm trying to mock some functions using cmocka:

...

ANSWER

Answered 2021-Jul-02 at 10:59

According to your test, it seams that function you are testing is led_status_toggel. If that is the case, you should not mock it. You should just remove will_return(led_status_toggel,SET);, since your led_status_toggel is probably something like this (You dind't share it so I don't know exactly):

Source https://stackoverflow.com/questions/68221813

QUESTION

libssh's functions couldn't be found on qt and cmake error while building libssh

Asked 2020-Jul-12 at 06:52

I want to use libssh library in Qt and my os is ubuntu 18.04 .
so I cloned the library's file and tried to build it with cmake. I followed the tutorial in INSTALL folder but the building process can't be completed.
at first I had this error :

...

ANSWER

Answered 2020-Jul-12 at 06:52

file INSTALL cannot copy file
"/home/heydari.f/libssh-mirror/build/libssh.pc" to
"/usr/local/lib/pkgconfig/libssh.pc"

This is a permissions issue. Use sudo make install to solve this. sudo gives root privileges to a command. Use it carefully.

** error: undefined reference to 'ssh_session_is_known_server'**

undefined reference usually means you are trying to access something, in this case a function, which is not found. This function belongs to libssh, so it means that either you don't have libssh-dev installed or you are giving the path to the library incorrectly. Since the latter is highly unlikely, i am going to assume libssh is missing. On Ubuntu you can install it using following command:

Source https://stackoverflow.com/questions/62857452

QUESTION

Understanding writing a CMakeLists.txt

Asked 2020-May-22 at 01:22

I have the following code that works perfectly with gcc by running the command:

...

ANSWER

Answered 2020-May-22 at 01:22

The include_directories() command only affects header search paths (stuff that is used through #include). It has no effect on library search paths.

Since you know the full path of the library, you should just be linking directly against said full path:

Source https://stackoverflow.com/questions/61944599

QUESTION

Cmocka unit testing with C: mocking nested function calls

Asked 2020-Mar-29 at 07:20

So, toy program that duplicates the issues I am having using cmocka for developing unit tests for existing code. The issue is a nested function call does not mock, which makes the unit test dependent on the nested function call performing properly. Please note, that "mockable_static" define was used as the original code has static functions that exist as "internal function calls", but for purposes of unit tests, these are open to external calls. (See stackoverflow post where this idea came from)

Without further ado, here is the code:

func.h:

...

ANSWER

Answered 2020-Feb-25 at 23:45

Alright, so there are a few different avenues to solve this problem. I am posting the solution so someone else can see this.

Solution #1: separate nested function calls into separate .c files. IE- func.c contains foo() and (newfile)bar.c contains bar(). This allows the GCC --wrap=bar to work within func.c as it needs to link against another file.

Solution #2: build separate tests for testing bar and foo. Use the following line in func.c to make bar "weak"

Source https://stackoverflow.com/questions/60400794

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install cmocka

You can download it from GitLab.

Support

For any new features, suggestions and bugs create an issue on GitLab. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: