74c09632 | 14-Nov-2016 |
Josh King <jdking@us.ibm.com> |
Implemented phosphor-event tests to gtest
This is the implemented portion of the tests over to gtest. As I have done previously I used test.C as a guide to complete the implementation of the tests.
Implemented phosphor-event tests to gtest
This is the implemented portion of the tests over to gtest. As I have done previously I used test.C as a guide to complete the implementation of the tests. One thing worth noting is that in the main method I had to modify the final few lines of code so that once the tests finished running, we would call setup() which clears the events created during this test. This is necessary so that if you were to run the tests a second time you wouldn't continue off from the previous event number you were at and instead you will now be starting fresh.
Resolved openbmc/openbmc#561
Change-Id: Ic192ac7753c7a9da541e8ed6efb272f43486ef95 Signed-off-by: Josh King <jdking@us.ibm.com>
show more ...
|
8761dbd8 | 11-Nov-2016 |
Josh King <jdking@us.ibm.com> |
Broke down our unit tests into gtest functions
I analyzed test.C to see which of the tests we had created and were running. I took the broken down tests and went over to the utest.cpp to start the
Broke down our unit tests into gtest functions
I analyzed test.C to see which of the tests we had created and were running. I took the broken down tests and went over to the utest.cpp to start the functions and listed them out. These functions still need to be implemented and that is my next step. I will use test.C to complete the implementation. This commit was merly only for the breaking down of the functions.
Change-Id: Ib3a75b3e2d4a7fba71b4ea337e552a4505100f5f Signed-off-by: Josh King <jdking@us.ibm.com>
show more ...
|