Thanks for your reply, Dieter
 
I will dig into the information that you gave me deeper. 
 
I am very familiar with the CI env and PHP code coverage, because I just finished a similiar project when I Intern on Yahoo! last year.
 
when I intern on Yahoo! last year, I finished a automatic testing job:
1. PHP UNIT code and Functional testing code.
2. Commit to SVN will trigger a CI build.
3. The CI build is done by: slenium + Firefox+ Xvfb (so that we dont need screen)
4. output the code coverage report.
 
adam
 
From: Dieter Adriaenssens
Date: 2013-03-19 17:49
To: adamgsoc2013; phpmyadmin-devel
Subject: Re: [Phpmyadmin-devel] new here for GSOC
2013/3/19 adam <adamgsoc2013@gmail.com>:
> Hi All,
>
> I am new here for GSOC.
> After reading the idea listed on link:
> https://wiki.phpmyadmin.net/pma/GSoC_2013_Ideas_List#Automated_testing
>
> I am quite interested on the topic: Automatic testing.  I have some
> developing experience on selenium and PHP Code Coverage.
>
> I am very glad to join phpmyadmin. I will dig my selves into here, thanks
>
> ________________________________
> adam
 
Hi,
 
If you are interested in applying for a GSoC project, you can take
a look at our applicant guide [0], it will tell you what we expect
from applicants.
In case of the automated testing idea : A good way to start is to have
a look at the current tests [1] and code coverage [2]. We expect you
to provide a patch as part of your project proposal, so you can add a
few tests to show us that you understand the code.
 
[0] http://wiki.phpmyadmin.net/pma/GSoC_2013_Applicant_Guide
[1] http://wiki.phpmyadmin.net/pma/Unit_Testing
[2] http://ci.phpmyadmin.net/job/phpMyAdmin/cloverphp
 
-- 
Kind regards,
 
Dieter Adriaenssens