[Shotwell] unit testing

[Jim Nelson]

Hi Bengt,

We are not using a test-driven design for Shotwell, nor do we have unit
tests prepared.  Rather, we're using an iterative approach of feature
additions and bug fixes.

We do have a ticket for an automated test suite (
http://trac.yorba.org/ticket/1068), but its intent is to find ways to
exercise Shotwell's capabilities and look for bugs, crashers, and unexpected
behavior (i.e. system testing, not unit testing).

I could see starting a suite of unit tests that begins small and works
outward and upward.  If you're interested, one good place to start would be
the Shotwell architecture pages on our wiki (
http://trac.yorba.org/wiki/ShotwellArchitectureOverview).  Shotwell has
smallish hard-working classes that could use validation (i.e. SortedList or
Command/CommandManager).  Unit tests could then work up to the central data
structures, DataObject and DataCollection, and beyond.

Unit testing would need to be in Vala; there's some support for GTest
already:

http://www.valadoc.org/glib-2.0/GLib.Test.html
http://live.gnome.org/Vala/TestSample

-- Jim

On Sat, Apr 17, 2010 at 8:09 PM, Bengt Thuree <bengt at thuree.com> wrote:

> Hi
>
> Just wondering if you are using a test driven design approach when you are
> designing Shotwell? Like unit testing.
>
> /Bengt
>
>
> --
> Bengt Thuree   bengt at thuree.com
>
> _______________________________________________
> Shotwell mailing list
> Shotwell at lists.yorba.org
> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
>