2nd part of the project – testing at the function level

I must say it was very hard for me at the beginning to determine what functions are more important and what are less but over time I started to recognize that. I will use the Boost Test Library for unit testing, for organizing tests CTest form CMake would be better because the first part of this project was based on it. Why Boost Test Library?

it is rather mature and stable

it has many information and examples of its usage

it has all the options needed for automatic testing

it has many additional options which might be used in future tests development

almost everyone have boost library already in their computer, so no additional installations are needed

Now some more about the tests. Here is a list I made myself for marking the priority of the testing files in libpano (the more ‘+’ the more it is important to test):

adjust.c +++

bmp.c +

ColourBrightness.c+++

correct.c ++

dump.c +

fftn.c +

file.c ++

filter.c ++++

fourier.c +

hdrfile.c +

javastub.c +

jpeg.c +

jpegicc.c +

lmdif.c +

math.c ++

metadata.c +++

morpher.c +

multilayer.c +

optimize.c +++

pan.c +

PaniniGeneral.c +

parser.c +

perspect.c +

png.c +

ppm.c +

PTcommon.c ++++

PTDialogs.c +

pteditor.c +

ptfeather.c +++

ptpicker.c ++

ptstitch.c +++

queryfeature.c ++

remap.c ++

resample.c ++

rgbe.c +

seamer_.c +

seamer.c +

shell_mac.c +

sys_ansi.c +

sys_common.c +

sys_mac.c +

sys_win.c +

sys_X11.c +

tiff.c +++

Triangulate.c +

ZComb.c +

That is quite a big list but it is almost impossible to test every function from this files fully. So it is important to choice wisely. And now a bit smaller list with functions I will test in the next days (or already started testing):