Hi,
I have recently cloned the phpMyAdmin repository and I am looking for some bugs or features requests to do which need attention and are higher in priority. What section of the bug tracker should I generally scan? I am also looking forward to applying as a student for Google Summer of Code 2013 under the task related to adding unit tests and automating tests using selenium tests.
But to gain familiarity, I would like to submit some required patches or feature-requests to start with. Is this the correct approach?
Thanks!
Ayush Chaudhary a écrit :
Hi,
I have recently cloned the phpMyAdmin repository and I am looking for some bugs or features requests to do which need attention and are higher in priority. What section of the bug tracker should I generally scan? I am also looking forward to applying as a student for Google Summer of Code 2013 under the task related to adding unit tests and automating tests using selenium tests.
But to gain familiarity, I would like to submit some required patches or feature-requests to start with. Is this the correct approach?
Yes, this is the correct approach. See [0]. Why not gaining familiarity by adding a few unit tests?
[0] http://wiki.phpmyadmin.net/pma/GSoC_2013_Applicant_Guide#Get_involved_with_p...
Thank you Marc.
Yes, I think I should be adding unit tests as well. Actually, I read somewhere only students who have submitted patches would be considered for GSoC, hence I was keen to do a few quick contributions and then once I was eligible, completely devote my time on Unit Testing.
-- Ayush Chaudhary
On Wednesday, 6 February 2013 at 2:03 AM, Marc Delisle wrote:
Ayush Chaudhary a écrit :
Hi,
I have recently cloned the phpMyAdmin repository and I am looking for some bugs or features requests to do which need attention and are higher in priority. What section of the bug tracker should I generally scan? I am also looking forward to applying as a student for Google Summer of Code 2013 under the task related to adding unit tests and automating tests using selenium tests.
But to gain familiarity, I would like to submit some required patches or feature-requests to start with. Is this the correct approach?
Yes, this is the correct approach. See [0]. Why not gaining familiarity by adding a few unit tests?
[0] http://wiki.phpmyadmin.net/pma/GSoC_2013_Applicant_Guide#Get_involved_with_p...
-- Marc Delisle http://infomarc.info
Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net (mailto:Phpmyadmin-devel@lists.sourceforge.net) https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
2013/2/5 Ayush Chaudhary ayushchd@gmail.com:
Thank you Marc.
Yes, I think I should be adding unit tests as well. Actually, I read somewhere only students who have submitted patches would be considered for GSoC, hence I was keen to do a few quick contributions and then once I was eligible, completely devote my time on Unit Testing.
Hi,
We consider new Unit/Selenium Tests as a valid patch. Certainly if you plan to apply for the automated testing GSoC project. Providing working unit tests shows us that you understand this. Have a look at the code coverage reports [0] to find untested code.
Of course, you are free to submit other patches (fixing bugs/adding features) as well, if that helps you to get familiar with the code. But emphasize on writing tests.
[0] http://ci.phpmyadmin.net/job/phpMyAdmin/cloverphp
Hi Dieter,
Thanks for the suggestion. That link is really really useful. I will try and start with Unit/Selenium Tests as soon as possible and provide some new Tests to increase the code coverage.
Thanks again!
-
Ayush Chaudhary -
Dieter Adriaenssens -
Marc Delisle