-
Notifications
You must be signed in to change notification settings - Fork 6
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
Unit Testing #4
Comments
In trying to unit test EventMgr I ran into the fact that there was so much infrastructure required, it just didn't make sense. Alternatives are:1) to build shim of EBBMgr, MMgr to test, 2) to build simple bring up, e.g., UP, that gets real ones working, 3) to modify EventMgr so that it calls a very surcomscribed set of interfaces, overridden in test. I am leaning towards option 2, but want to discuss before proceed. I think, while this is doing somewhat of a integration test, given that we rely on some core objects, this is the most natural. |
this will be used for integration tests, and will be used for regression |
Had to modify a bunch of files to allow c++ linkage. Removed the old testing. Also modified build to allow configure to still work without cppunit
Not happy with it as it is. We may as well do away with the framework as far as I'm concerned. Maybe someone can take a look and give a second opinion. |
Skype me if you are free this aft, and lets discuss, expect to be back at work mid-aft |
…e what we are doing here. See Issue #4.
How do we want to do unit testing of our code?
I suggest cppunit. Will mock up some code as an example
The text was updated successfully, but these errors were encountered: