Some of the SDL examples are still subject of bitrot. Especially the more
complex ones like tetris and minesweeper.
We need tests.
1) Basic tests for all SDL classes and interfaces. There's no GUI involved at
all at this step. Just a test if constructors, methods, or attribute
accessors are working/implemented as specced.
2) The more daunting task of testing full-fledged examples or even SDL
applications. We probably don't have serious GUI tests for a forseeable time,
but we can still test, if an application at least starts properly before
possibly entering the event handler loop.
E.g. sdl/mandel.pir can be started like this:
./parrot examples/sdl/mandel.pir --quit
It'll draw the default mandel set picture and terminate immediately.
We can of course mandate that any testable sdl example/app (i.e all ;) provide
processing of:
./parrot examples/sdl/mandel.pir --test_quit
or some such, which should spit out a single string "test_ok\n" to stdout.
This string result can be tested for with standard TAP means.
3) and future ... testing if the GUI of the app really works
Thanks,
leo
We need a config test first, if SDL is present and working, which shall
define:
C defines perl5
PARROT_HAS_SDL HAS_SDL
PARROT_HAS_SDL_image HAS_SDL_image
(It's not given that libSDL_image is present, *if* libSDL is installed)
leo