-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create automatic software tests for variod #23
Comments
@kedder : How can we integrate these tests into Github CI ? Think there should be a way to start the tools with one single command and got a result back after the test. |
There is no tests yet, the tool I made so far is for "manual" testing - so I can squeeze some sound from the variod on my laptop (without real sensord). Once we have some automated tests, it should be pretty easy to integrate them with CI. |
@kedder : What do you think about Mock testing ?? |
@linuxianer99, I think mocking i2c might only be relevant for testing sensord. Input for variod is NMEA stream, and output is NMEA too, so no harware mocking is really needed here. |
@kedder : you are right regarding I2c. But i think we should use just one test framework for both apps. |
I don't disagree. I don't have any experience with unit testing C programs, so I don't have a strong opinion here. |
I also have less experience with testing C programs. https://www.wfbsoftware.de/2019/07/18/c-unit-testing-with-cmocka/ Have the first test running in sensord. (AirDensity functions): ` #include "../AirDensity.h" static void test_AirDensity() int main(int argc, char **argv) It's without mock, but very simple to implement .. The output look like: `[build@localhost sensord]$ ./testmain 0 FAILED TEST(S) I can prepare something the next days and push it in a branch. So you can have a look on it ... |
Maybe we can use a framework like Robot framework https://robotframework.org/
The text was updated successfully, but these errors were encountered: