On Sun, 2015-05-17 at 07:04 -0500, Daniel Espinosa wrote:
I think your idea of keep processes in a library and create unit tests
to it and then link to your GUI app is the better approach.
GDA[1] have a processes non-GUI library, a GUI library of widgets and
a GUI app. You should check it.
I think your idea of keep processes in a library and create unit tests to
it and then link to your GUI app is the better approach.
GDA[1] have a processes non-GUI library, a GUI library of widgets and a GUI
app. You should check it.
[1] git.gnome.org/browse/libgda
El may 16, 2015 4:45 AM, John
On 05/16/2015 11:45 AM, John Tall wrote:
This time however I'm building an application, so it will already have
its own main routine. I can't link my unit tests to the application
because that would give me two main routines, the main entry point of
the application and the main entry point of
you also might want to have a look at google test. at first glance, it
seems to satisfy your needs:
http://en.wikipedia.org/wiki/Google_Test
On Sat, May 16, 2015 at 4:45 AM, John Tall mjta...@gmail.com wrote:
Hello.
I'm about to start working on a new GTK+ application that will be
written
Hello.
I'm about to start working on a new GTK+ application that will be
written in C. I want to use unit tests, probably the GTest APIs from
GLib.
I've used the GTest APIs before when building a library. What I did
then was that I put all the source code for the library in one
directory, all
