Re: [Freetype-devel] Re: Develop a test framework for checking FreeType's rendering output - GSoC Project

[suzuki toshiya]

Dear Sarthak,

It seems that you think as - the FreeType is a huge software which the compiler 
generates so many warnings, like uninitialized variable, passing the 
inappropriate typed values, etc etc, and some of them are related with the 
rasterization results. It is not. Even if you try to extract something from the 
compiler warning messages, most of them are not related with the difference in 
the rasterization results between version X and version Y, although some of 
them can be related with the software vulnerabilities.

The assumed testing framework is basically for the minimization of the regression of the rasterized image, not the "code 
quality" or "secure coding" itself. If the "code quality" or "secure coding" is at the highest 
priority, what we need is more generic inspector, instead of the FreeType-specific framework. The assumed "testing" in 
the GSoC theme is basically the rasterization results.

Regards,
mpsuzuki

On 2021/03/22 4:22, sarthak bhardwaj wrote:
> hello werner,
> I think I could be explained earlier in detail from my side, sorry for that if 
> I am not getting it wrong, In this project( as far I have observed) the 
> sequence should be like that -
>
>
>    *   firstly we need to set up continuous integration services compatible 
> with GitLab.
>    *   After setting up we need to add compilation and some desired 
> functionality tests to our code, along with these services we can use a custom 
> test harness(It is a collection of software and test data configured to test a 
> program unit by running it under varying conditions and monitoring its behavior 
> and outputs. ... Test harnesses allow for the automation of tests.) to check 
> for compile errors.
>
>
> This is my opinion about it, I might be wrong, Please correct me if I have 
> misunderstood the thing, and do suggest your opinion about this
>
> Thanks in advance :)
> Sarthak Bhardwaj