views:

2825

answers:

4

We need to write unit tests for a wxWidgets application using Google Test Framework. The problem is that wxWidgets uses the macro IMPLEMENT_APP(MyApp) to initialize and enter the application main loop. This macro creates several functions including int main(). The google test framework also uses macro definitions for each test.

One of the problems is that it is not possible to call the wxWidgets macro from within the test macro, because the first one creates functions.. So, we found that we could replace the macro with the following code:

wxApp* pApp = new MyApp(); 
wxApp::SetInstance(pApp);
wxEntry(argc, argv);

That's a good replacement, but wxEntry() call enters the original application loop. If we don't call wxEntry() there are still some parts of the application not initialized.

The question is how to initialize everything required for a wxApp to run, without actually running it, so we are able to unit test portions of it?

A: 

You could possibly turn the situation around:

Initialize and start the wxPython app including the main loop, then run the unit tests from within the app. I think there is a function called upon main loop entry, after all init stuff is done.

Ber
The goal is to test the application with UT, not UT with app
m_pGladiator
Unless you find a way to do the complete init (and so far nobody suggested a viable solution)The goal that was stated in a comment above can well be achieved this way. I have done similar things already in wxPython.
Ber
+1 from me, this is how I did my tests in wxWidgets after trying to solve the problem myself.
SteveL
A: 

Have you tried the IMPLEMENT_APP_NO_MAIN macro? The comment provided above the macro definition suggests it might do what you need it to.

From <wxWidgets' source dir>\include\wx.h:

// Use this macro if you want to define your own main() or WinMain() function
// and call wxEntry() from there.
#define IMPLEMENT_APP_NO_MAIN(appname)                                      \
   wxAppConsole *wxCreateApp()                                             \
    {                                                                       \
        wxAppConsole::CheckBuildOptions(WX_BUILD_OPTIONS_SIGNATURE,         \
                                        "your program");                    \
        return new appname;                                                 \
    }                                                                       \
    wxAppInitializer                                                        \
        wxTheAppInitializer((wxAppInitializerFunction) wxCreateApp);        \
    DECLARE_APP(appname)                                                    \
    appname& wxGetApp() { return *wx_static_cast(appname*, wxApp::GetInstance()); }
antik
This macro is actually reduced to the first two lines of code in the question. The problem is that before calling wxEntry() there are some parts of wxApp still not initialized. wxEntry() enters the app loop and the control is passed to wxWidgets. I'd like to init the wxApp, without running it.
m_pGladiator
A: 

You want to use the function:

bool wxEntryStart(int& argc, wxChar **argv)

instead of wxEntry. It doesn't call your app's OnInit() or run the main loop.

You can call wxTheApp->CallOnInit() to invoke OnInit() when needed in your tests.

You'll need to use

void wxEntryCleanup()

when you're done.

kbluck
Actually, this does not work. The application is still not initialized
m_pGladiator
Can you be more specific about what "not initialized" means? If you read the source code, you will see that wxEntry really doesn't do much more than invoke wxEntryStart() and then call the "OnInit()" and "OnRun()". I would think you'd want to call OnInit() manually in your tests.
kbluck
OK, that's something I missed - OnInit(). I'll try it.
m_pGladiator
By Initialized, means I could create a main window, without showing it and keeping control in the UT, which enables the UT to create classes, which requires this main window in order to work.
m_pGladiator
Main windows are conventionally created in OnInit(). You can call wxTheApp->CallOnInit() to invoke it manually.However, if the message pump is not running, most event-related parts of the window will not work. Perhaps this topic is moving into a new, different question about how to unit test GUIs?
kbluck
+2  A: 

Just been through this myself with 2.8.10. The magic is this:

// MyWxApp derives from wxApp
wxApp::SetInstance( new MyWxApp() );
wxEntryStart( argc, argv );
wxTheApp->OnInit();

// you can create top level-windows here or in OnInit()
...
// do your testing here

wxTheApp->OnRun();
wxTheApp->OnExit();
wxEntryCleanup();

You can just create a wxApp instance rather than deriving your own class using the technique above.

I'm not sure how you expect to do unit testing of your application without entering the mainloop as many wxWidgets components require the delivery of events to function. The usual approach would be to run unit tests after entering the main loop.

Daniel Paull